Поиск уязвимостей
Количество 23
Количество 23
CVE-2023-52699
In the Linux kernel, the following vulnerability has been resolved: sysv: don't call sb_bread() with pointers_lock held syzbot is reporting sleep in atomic context in SysV filesystem [1], for sb_bread() is called with rw_spinlock held. A "write_lock(&pointers_lock) => read_lock(&pointers_lock) deadlock" bug and a "sb_bread() with write_lock(&pointers_lock)" bug were introduced by "Replace BKL for chain locking with sysvfs-private rwlock" in Linux 2.5.12. Then, "[PATCH] err1-40: sysvfs locking fix" in Linux 2.6.8 fixed the former bug by moving pointers_lock lock to the callers, but instead introduced a "sb_bread() with read_lock(&pointers_lock)" bug (which made this problem easier to hit). Al Viro suggested that why not to do like get_branch()/get_block()/ find_shared() in Minix filesystem does. And doing like that is almost a revert of "[PATCH] err1-40: sysvfs locking fix" except that get_branch() from with find_shared() is called without write_lock(&pointers_lock).
CVE-2023-52699
In the Linux kernel, the following vulnerability has been resolved: sysv: don't call sb_bread() with pointers_lock held syzbot is reporting sleep in atomic context in SysV filesystem [1], for sb_bread() is called with rw_spinlock held. A "write_lock(&pointers_lock) => read_lock(&pointers_lock) deadlock" bug and a "sb_bread() with write_lock(&pointers_lock)" bug were introduced by "Replace BKL for chain locking with sysvfs-private rwlock" in Linux 2.5.12. Then, "[PATCH] err1-40: sysvfs locking fix" in Linux 2.6.8 fixed the former bug by moving pointers_lock lock to the callers, but instead introduced a "sb_bread() with read_lock(&pointers_lock)" bug (which made this problem easier to hit). Al Viro suggested that why not to do like get_branch()/get_block()/ find_shared() in Minix filesystem does. And doing like that is almost a revert of "[PATCH] err1-40: sysvfs locking fix" except that get_branch() from with find_shared() is called without write_lock(&pointers_lock).
CVE-2023-52699
In the Linux kernel, the following vulnerability has been resolved: sysv: don't call sb_bread() with pointers_lock held syzbot is reporting sleep in atomic context in SysV filesystem [1], for sb_bread() is called with rw_spinlock held. A "write_lock(&pointers_lock) => read_lock(&pointers_lock) deadlock" bug and a "sb_bread() with write_lock(&pointers_lock)" bug were introduced by "Replace BKL for chain locking with sysvfs-private rwlock" in Linux 2.5.12. Then, "[PATCH] err1-40: sysvfs locking fix" in Linux 2.6.8 fixed the former bug by moving pointers_lock lock to the callers, but instead introduced a "sb_bread() with read_lock(&pointers_lock)" bug (which made this problem easier to hit). Al Viro suggested that why not to do like get_branch()/get_block()/ find_shared() in Minix filesystem does. And doing like that is almost a revert of "[PATCH] err1-40: sysvfs locking fix" except that get_branch() from with find_shared() is called without write_lock(&pointers_lock).
CVE-2023-52699
In the Linux kernel, the following vulnerability has been resolved: s ...
GHSA-29pq-gr25-8674
In the Linux kernel, the following vulnerability has been resolved: sysv: don't call sb_bread() with pointers_lock held syzbot is reporting sleep in atomic context in SysV filesystem [1], for sb_bread() is called with rw_spinlock held. A "write_lock(&pointers_lock) => read_lock(&pointers_lock) deadlock" bug and a "sb_bread() with write_lock(&pointers_lock)" bug were introduced by "Replace BKL for chain locking with sysvfs-private rwlock" in Linux 2.5.12. Then, "[PATCH] err1-40: sysvfs locking fix" in Linux 2.6.8 fixed the former bug by moving pointers_lock lock to the callers, but instead introduced a "sb_bread() with read_lock(&pointers_lock)" bug (which made this problem easier to hit). Al Viro suggested that why not to do like get_branch()/get_block()/ find_shared() in Minix filesystem does. And doing like that is almost a revert of "[PATCH] err1-40: sysvfs locking fix" except that get_branch() from with find_shared() is called without write_lock(&pointers_lock).
BDU:2024-09808
Уязвимость компонента sysv ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ALT-PU-2024-18368
ALT-PU-2024-18368: package `kernel-image-std-def` update to version 6.1.86-alt1
ROS-20241114-01
Множественные уязвимости kernel-lt
ALT-PU-2024-6507
ALT-PU-2024-6507: package `kernel-image-un-def` update to version 6.6.27-alt1
ALT-PU-2024-6505
ALT-PU-2024-6505: package `kernel-image-6.8` update to version 6.8.6-alt1
ALT-PU-2024-17905
ALT-PU-2024-17905: package `kernel-image-un-def` update to version 6.1.90-alt1
ALT-PU-2024-18077
ALT-PU-2024-18077: package `kernel-image-rt` update to version 5.10.215-alt1.rt107
SUSE-SU-2024:2571-1
Security update for the Linux Kernel
ALT-PU-2024-18212
ALT-PU-2024-18212: package `kernel-image-pine` update to version 6.6.27-alt1
ALT-PU-2024-18118
ALT-PU-2024-18118: package `kernel-image-mp` update to version 6.8.8-alt1
ALT-PU-2024-7511
ALT-PU-2024-7511: package `kernel-image-std-def` update to version 5.10.216-alt1
ALT-PU-2024-7646
ALT-PU-2024-7646: package `kernel-image-rt` update to version 6.1.90-alt1.rt30
SUSE-SU-2024:2896-1
Security update for the Linux Kernel
SUSE-SU-2024:2019-1
Security update for the Linux Kernel
SUSE-SU-2024:2190-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2023-52699 In the Linux kernel, the following vulnerability has been resolved: sysv: don't call sb_bread() with pointers_lock held syzbot is reporting sleep in atomic context in SysV filesystem [1], for sb_bread() is called with rw_spinlock held. A "write_lock(&pointers_lock) => read_lock(&pointers_lock) deadlock" bug and a "sb_bread() with write_lock(&pointers_lock)" bug were introduced by "Replace BKL for chain locking with sysvfs-private rwlock" in Linux 2.5.12. Then, "[PATCH] err1-40: sysvfs locking fix" in Linux 2.6.8 fixed the former bug by moving pointers_lock lock to the callers, but instead introduced a "sb_bread() with read_lock(&pointers_lock)" bug (which made this problem easier to hit). Al Viro suggested that why not to do like get_branch()/get_block()/ find_shared() in Minix filesystem does. And doing like that is almost a revert of "[PATCH] err1-40: sysvfs locking fix" except that get_branch() from with find_shared() is called without write_lock(&pointers_lock). | CVSS3: 5.3 | 1% Низкий | больше 2 лет назад | |
CVE-2023-52699 In the Linux kernel, the following vulnerability has been resolved: sysv: don't call sb_bread() with pointers_lock held syzbot is reporting sleep in atomic context in SysV filesystem [1], for sb_bread() is called with rw_spinlock held. A "write_lock(&pointers_lock) => read_lock(&pointers_lock) deadlock" bug and a "sb_bread() with write_lock(&pointers_lock)" bug were introduced by "Replace BKL for chain locking with sysvfs-private rwlock" in Linux 2.5.12. Then, "[PATCH] err1-40: sysvfs locking fix" in Linux 2.6.8 fixed the former bug by moving pointers_lock lock to the callers, but instead introduced a "sb_bread() with read_lock(&pointers_lock)" bug (which made this problem easier to hit). Al Viro suggested that why not to do like get_branch()/get_block()/ find_shared() in Minix filesystem does. And doing like that is almost a revert of "[PATCH] err1-40: sysvfs locking fix" except that get_branch() from with find_shared() is called without write_lock(&pointers_lock). | CVSS3: 5.5 | 1% Низкий | больше 2 лет назад | |
CVE-2023-52699 In the Linux kernel, the following vulnerability has been resolved: sysv: don't call sb_bread() with pointers_lock held syzbot is reporting sleep in atomic context in SysV filesystem [1], for sb_bread() is called with rw_spinlock held. A "write_lock(&pointers_lock) => read_lock(&pointers_lock) deadlock" bug and a "sb_bread() with write_lock(&pointers_lock)" bug were introduced by "Replace BKL for chain locking with sysvfs-private rwlock" in Linux 2.5.12. Then, "[PATCH] err1-40: sysvfs locking fix" in Linux 2.6.8 fixed the former bug by moving pointers_lock lock to the callers, but instead introduced a "sb_bread() with read_lock(&pointers_lock)" bug (which made this problem easier to hit). Al Viro suggested that why not to do like get_branch()/get_block()/ find_shared() in Minix filesystem does. And doing like that is almost a revert of "[PATCH] err1-40: sysvfs locking fix" except that get_branch() from with find_shared() is called without write_lock(&pointers_lock). | CVSS3: 5.3 | 1% Низкий | больше 2 лет назад | |
CVE-2023-52699 In the Linux kernel, the following vulnerability has been resolved: s ... | CVSS3: 5.3 | 1% Низкий | больше 2 лет назад | |
GHSA-29pq-gr25-8674 In the Linux kernel, the following vulnerability has been resolved: sysv: don't call sb_bread() with pointers_lock held syzbot is reporting sleep in atomic context in SysV filesystem [1], for sb_bread() is called with rw_spinlock held. A "write_lock(&pointers_lock) => read_lock(&pointers_lock) deadlock" bug and a "sb_bread() with write_lock(&pointers_lock)" bug were introduced by "Replace BKL for chain locking with sysvfs-private rwlock" in Linux 2.5.12. Then, "[PATCH] err1-40: sysvfs locking fix" in Linux 2.6.8 fixed the former bug by moving pointers_lock lock to the callers, but instead introduced a "sb_bread() with read_lock(&pointers_lock)" bug (which made this problem easier to hit). Al Viro suggested that why not to do like get_branch()/get_block()/ find_shared() in Minix filesystem does. And doing like that is almost a revert of "[PATCH] err1-40: sysvfs locking fix" except that get_branch() from with find_shared() is called without write_lock(&pointers_lock). | CVSS3: 5.3 | 1% Низкий | больше 2 лет назад | |
BDU:2024-09808 Уязвимость компонента sysv ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 1% Низкий | почти 3 года назад | |
ALT-PU-2024-18368 ALT-PU-2024-18368: package `kernel-image-std-def` update to version 6.1.86-alt1 | CVSS3: 7.8 | больше 2 лет назад | ||
ROS-20241114-01 Множественные уязвимости kernel-lt | CVSS3: 8.8 | почти 2 года назад | ||
ALT-PU-2024-6507 ALT-PU-2024-6507: package `kernel-image-un-def` update to version 6.6.27-alt1 | CVSS3: 7.8 | больше 2 лет назад | ||
ALT-PU-2024-6505 ALT-PU-2024-6505: package `kernel-image-6.8` update to version 6.8.6-alt1 | CVSS3: 7.8 | больше 2 лет назад | ||
ALT-PU-2024-17905 ALT-PU-2024-17905: package `kernel-image-un-def` update to version 6.1.90-alt1 | CVSS3: 9.1 | больше 1 года назад | ||
ALT-PU-2024-18077 ALT-PU-2024-18077: package `kernel-image-rt` update to version 5.10.215-alt1.rt107 | CVSS3: 9.1 | больше 2 лет назад | ||
SUSE-SU-2024:2571-1 Security update for the Linux Kernel | больше 2 лет назад | |||
ALT-PU-2024-18212 ALT-PU-2024-18212: package `kernel-image-pine` update to version 6.6.27-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-18118 ALT-PU-2024-18118: package `kernel-image-mp` update to version 6.8.8-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-7511 ALT-PU-2024-7511: package `kernel-image-std-def` update to version 5.10.216-alt1 | CVSS3: 9.1 | больше 2 лет назад | ||
ALT-PU-2024-7646 ALT-PU-2024-7646: package `kernel-image-rt` update to version 6.1.90-alt1.rt30 | CVSS3: 9.8 | больше 2 лет назад | ||
SUSE-SU-2024:2896-1 Security update for the Linux Kernel | около 2 лет назад | |||
SUSE-SU-2024:2019-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:2190-1 Security update for the Linux Kernel | больше 2 лет назад |
Уязвимостей на страницу