Поиск уязвимостей
Количество 23
Количество 23
CVE-2025-21664
In the Linux kernel, the following vulnerability has been resolved: dm thin: make get_first_thin use rcu-safe list first function The documentation in rculist.h explains the absence of list_empty_rcu() and cautions programmers against relying on a list_empty() -> list_first() sequence in RCU safe code. This is because each of these functions performs its own READ_ONCE() of the list head. This can lead to a situation where the list_empty() sees a valid list entry, but the subsequent list_first() sees a different view of list head state after a modification. In the case of dm-thin, this author had a production box crash from a GP fault in the process_deferred_bios path. This function saw a valid list head in get_first_thin() but when it subsequently dereferenced that and turned it into a thin_c, it got the inside of the struct pool, since the list was now empty and referring to itself. The kernel on which this occurred printed both a warning about a refcount_t being saturated, and...
CVE-2025-21664
In the Linux kernel, the following vulnerability has been resolved: dm thin: make get_first_thin use rcu-safe list first function The documentation in rculist.h explains the absence of list_empty_rcu() and cautions programmers against relying on a list_empty() -> list_first() sequence in RCU safe code. This is because each of these functions performs its own READ_ONCE() of the list head. This can lead to a situation where the list_empty() sees a valid list entry, but the subsequent list_first() sees a different view of list head state after a modification. In the case of dm-thin, this author had a production box crash from a GP fault in the process_deferred_bios path. This function saw a valid list head in get_first_thin() but when it subsequently dereferenced that and turned it into a thin_c, it got the inside of the struct pool, since the list was now empty and referring to itself. The kernel on which this occurred printed both a warning about a refcount_t being saturated, and...
CVE-2025-21664
In the Linux kernel, the following vulnerability has been resolved: dm thin: make get_first_thin use rcu-safe list first function The documentation in rculist.h explains the absence of list_empty_rcu() and cautions programmers against relying on a list_empty() -> list_first() sequence in RCU safe code. This is because each of these functions performs its own READ_ONCE() of the list head. This can lead to a situation where the list_empty() sees a valid list entry, but the subsequent list_first() sees a different view of list head state after a modification. In the case of dm-thin, this author had a production box crash from a GP fault in the process_deferred_bios path. This function saw a valid list head in get_first_thin() but when it subsequently dereferenced that and turned it into a thin_c, it got the inside of the struct pool, since the list was now empty and referring to itself. The kernel on which this occurred printed both a warning about a refcount_t being saturated, and
CVE-2025-21664
In the Linux kernel, the following vulnerability has been resolved: d ...
GHSA-vp4f-mc7f-v3pc
In the Linux kernel, the following vulnerability has been resolved: dm thin: make get_first_thin use rcu-safe list first function The documentation in rculist.h explains the absence of list_empty_rcu() and cautions programmers against relying on a list_empty() -> list_first() sequence in RCU safe code. This is because each of these functions performs its own READ_ONCE() of the list head. This can lead to a situation where the list_empty() sees a valid list entry, but the subsequent list_first() sees a different view of list head state after a modification. In the case of dm-thin, this author had a production box crash from a GP fault in the process_deferred_bios path. This function saw a valid list head in get_first_thin() but when it subsequently dereferenced that and turned it into a thin_c, it got the inside of the struct pool, since the list was now empty and referring to itself. The kernel on which this occurred printed both a warning about a refcount_t being saturated, ...
BDU:2025-06548
Уязвимость компонента dm thin ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ALT-PU-2025-3122
ALT-PU-2025-3122: package `kernel-image-rt` update to version 5.10.234-alt1.rt126
ALT-PU-2025-2417
ALT-PU-2025-2417: package `kernel-image-std-def` update to version 5.10.234-alt1
ROS-20250514-01
Множественные уязвимости kernel-lt
SUSE-SU-2025:0565-1
Security update for the Linux Kernel
SUSE-SU-2025:0564-1
Security update for the Linux Kernel
ALT-PU-2025-1861
ALT-PU-2025-1861: package `kernel-image-un-def` update to version 6.1.127-alt1
ALT-PU-2025-3500
ALT-PU-2025-3500: package `kernel-image-6.6` update to version 6.6.74-alt1
ALT-PU-2025-3467
ALT-PU-2025-3467: package `kernel-image-6.12` update to version 6.12.11-alt1
ALT-PU-2025-1980
ALT-PU-2025-1980: package `kernel-image-pine` update to version 6.12.11-alt1
SUSE-SU-2025:0428-1
Security update for the Linux Kernel
SUSE-SU-2025:0557-1
Security update for the Linux Kernel
SUSE-SU-2025:0499-1
Security update for the Linux Kernel
ALT-PU-2025-1925
ALT-PU-2025-1925: package `kernel-image-rt` update to version 6.12.11-alt1
ELSA-2025-20530
ELSA-2025-20530: Unbreakable Enterprise kernel security update (IMPORTANT)
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2025-21664 In the Linux kernel, the following vulnerability has been resolved: dm thin: make get_first_thin use rcu-safe list first function The documentation in rculist.h explains the absence of list_empty_rcu() and cautions programmers against relying on a list_empty() -> list_first() sequence in RCU safe code. This is because each of these functions performs its own READ_ONCE() of the list head. This can lead to a situation where the list_empty() sees a valid list entry, but the subsequent list_first() sees a different view of list head state after a modification. In the case of dm-thin, this author had a production box crash from a GP fault in the process_deferred_bios path. This function saw a valid list head in get_first_thin() but when it subsequently dereferenced that and turned it into a thin_c, it got the inside of the struct pool, since the list was now empty and referring to itself. The kernel on which this occurred printed both a warning about a refcount_t being saturated, and... | CVSS3: 5.5 | 0% Низкий | почти 2 года назад | |
CVE-2025-21664 In the Linux kernel, the following vulnerability has been resolved: dm thin: make get_first_thin use rcu-safe list first function The documentation in rculist.h explains the absence of list_empty_rcu() and cautions programmers against relying on a list_empty() -> list_first() sequence in RCU safe code. This is because each of these functions performs its own READ_ONCE() of the list head. This can lead to a situation where the list_empty() sees a valid list entry, but the subsequent list_first() sees a different view of list head state after a modification. In the case of dm-thin, this author had a production box crash from a GP fault in the process_deferred_bios path. This function saw a valid list head in get_first_thin() but when it subsequently dereferenced that and turned it into a thin_c, it got the inside of the struct pool, since the list was now empty and referring to itself. The kernel on which this occurred printed both a warning about a refcount_t being saturated, and... | CVSS3: 4.4 | 0% Низкий | почти 2 года назад | |
CVE-2025-21664 In the Linux kernel, the following vulnerability has been resolved: dm thin: make get_first_thin use rcu-safe list first function The documentation in rculist.h explains the absence of list_empty_rcu() and cautions programmers against relying on a list_empty() -> list_first() sequence in RCU safe code. This is because each of these functions performs its own READ_ONCE() of the list head. This can lead to a situation where the list_empty() sees a valid list entry, but the subsequent list_first() sees a different view of list head state after a modification. In the case of dm-thin, this author had a production box crash from a GP fault in the process_deferred_bios path. This function saw a valid list head in get_first_thin() but when it subsequently dereferenced that and turned it into a thin_c, it got the inside of the struct pool, since the list was now empty and referring to itself. The kernel on which this occurred printed both a warning about a refcount_t being saturated, and | CVSS3: 5.5 | 0% Низкий | почти 2 года назад | |
CVE-2025-21664 In the Linux kernel, the following vulnerability has been resolved: d ... | CVSS3: 5.5 | 0% Низкий | почти 2 года назад | |
GHSA-vp4f-mc7f-v3pc In the Linux kernel, the following vulnerability has been resolved: dm thin: make get_first_thin use rcu-safe list first function The documentation in rculist.h explains the absence of list_empty_rcu() and cautions programmers against relying on a list_empty() -> list_first() sequence in RCU safe code. This is because each of these functions performs its own READ_ONCE() of the list head. This can lead to a situation where the list_empty() sees a valid list entry, but the subsequent list_first() sees a different view of list head state after a modification. In the case of dm-thin, this author had a production box crash from a GP fault in the process_deferred_bios path. This function saw a valid list head in get_first_thin() but when it subsequently dereferenced that and turned it into a thin_c, it got the inside of the struct pool, since the list was now empty and referring to itself. The kernel on which this occurred printed both a warning about a refcount_t being saturated, ... | CVSS3: 5.5 | 0% Низкий | почти 2 года назад | |
BDU:2025-06548 Уязвимость компонента dm thin ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 7.8 | 0% Низкий | почти 2 года назад | |
ALT-PU-2025-3122 ALT-PU-2025-3122: package `kernel-image-rt` update to version 5.10.234-alt1.rt126 | CVSS3: 8.8 | больше 1 года назад | ||
ALT-PU-2025-2417 ALT-PU-2025-2417: package `kernel-image-std-def` update to version 5.10.234-alt1 | CVSS3: 8.8 | больше 1 года назад | ||
ROS-20250514-01 Множественные уязвимости kernel-lt | CVSS3: 8 | больше 1 года назад | ||
SUSE-SU-2025:0565-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:0564-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2025-1861 ALT-PU-2025-1861: package `kernel-image-un-def` update to version 6.1.127-alt1 | CVSS3: 7.8 | почти 2 года назад | ||
ALT-PU-2025-3500 ALT-PU-2025-3500: package `kernel-image-6.6` update to version 6.6.74-alt1 | CVSS3: 7.8 | больше 1 года назад | ||
ALT-PU-2025-3467 ALT-PU-2025-3467: package `kernel-image-6.12` update to version 6.12.11-alt1 | CVSS3: 7.8 | больше 1 года назад | ||
ALT-PU-2025-1980 ALT-PU-2025-1980: package `kernel-image-pine` update to version 6.12.11-alt1 | CVSS3: 7.8 | почти 2 года назад | ||
SUSE-SU-2025:0428-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:0557-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:0499-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2025-1925 ALT-PU-2025-1925: package `kernel-image-rt` update to version 6.12.11-alt1 | CVSS3: 8 | почти 2 года назад | ||
ELSA-2025-20530 ELSA-2025-20530: Unbreakable Enterprise kernel security update (IMPORTANT) | около 1 года назад |
Уязвимостей на страницу