Количество 38
Количество 38

CVE-2024-42232
In the Linux kernel, the following vulnerability has been resolved: libceph: fix race between delayed_work() and ceph_monc_stop() The way the delayed work is handled in ceph_monc_stop() is prone to races with mon_fault() and possibly also finish_hunting(). Both of these can requeue the delayed work which wouldn't be canceled by any of the following code in case that happens after cancel_delayed_work_sync() runs -- __close_session() doesn't mess with the delayed work in order to avoid interfering with the hunting interval logic. This part was missed in commit b5d91704f53e ("libceph: behave in mon_fault() if cur_mon < 0") and use-after-free can still ensue on monc and objects that hang off of it, with monc->auth and monc->monmap being particularly susceptible to quickly being reused. To fix this: - clear monc->cur_mon and monc->hunting as part of closing the session in ceph_monc_stop() - bail from delayed_work() if monc->cur_mon is cleared, similar to how it's done in mon_fault() an...

CVE-2024-42232
In the Linux kernel, the following vulnerability has been resolved: libceph: fix race between delayed_work() and ceph_monc_stop() The way the delayed work is handled in ceph_monc_stop() is prone to races with mon_fault() and possibly also finish_hunting(). Both of these can requeue the delayed work which wouldn't be canceled by any of the following code in case that happens after cancel_delayed_work_sync() runs -- __close_session() doesn't mess with the delayed work in order to avoid interfering with the hunting interval logic. This part was missed in commit b5d91704f53e ("libceph: behave in mon_fault() if cur_mon < 0") and use-after-free can still ensue on monc and objects that hang off of it, with monc->auth and monc->monmap being particularly susceptible to quickly being reused. To fix this: - clear monc->cur_mon and monc->hunting as part of closing the session in ceph_monc_stop() - bail from delayed_work() if monc->cur_mon is cleared, similar to how it's done in mon_fault() an...

CVE-2024-42232
In the Linux kernel, the following vulnerability has been resolved: libceph: fix race between delayed_work() and ceph_monc_stop() The way the delayed work is handled in ceph_monc_stop() is prone to races with mon_fault() and possibly also finish_hunting(). Both of these can requeue the delayed work which wouldn't be canceled by any of the following code in case that happens after cancel_delayed_work_sync() runs -- __close_session() doesn't mess with the delayed work in order to avoid interfering with the hunting interval logic. This part was missed in commit b5d91704f53e ("libceph: behave in mon_fault() if cur_mon < 0") and use-after-free can still ensue on monc and objects that hang off of it, with monc->auth and monc->monmap being particularly susceptible to quickly being reused. To fix this: - clear monc->cur_mon and monc->hunting as part of closing the session in ceph_monc_stop() - bail from delayed_work() if monc->cur_mon is cleared, similar to how it's done in mon_fault

CVE-2024-42232
CVE-2024-42232
In the Linux kernel, the following vulnerability has been resolved: l ...
GHSA-5vqw-wppf-x433
In the Linux kernel, the following vulnerability has been resolved: libceph: fix race between delayed_work() and ceph_monc_stop() The way the delayed work is handled in ceph_monc_stop() is prone to races with mon_fault() and possibly also finish_hunting(). Both of these can requeue the delayed work which wouldn't be canceled by any of the following code in case that happens after cancel_delayed_work_sync() runs -- __close_session() doesn't mess with the delayed work in order to avoid interfering with the hunting interval logic. This part was missed in commit b5d91704f53e ("libceph: behave in mon_fault() if cur_mon < 0") and use-after-free can still ensue on monc and objects that hang off of it, with monc->auth and monc->monmap being particularly susceptible to quickly being reused. To fix this: - clear monc->cur_mon and monc->hunting as part of closing the session in ceph_monc_stop() - bail from delayed_work() if monc->cur_mon is cleared, similar to how it's done in mon_fa...

BDU:2024-08326
Уязвимость функции ceph_monc_stop() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании

SUSE-SU-2025:02422-1
Security update for the Linux Kernel (Live Patch 57 for SLE 12 SP5)

SUSE-SU-2025:02392-1
Security update for the Linux Kernel (Live Patch 59 for SLE 12 SP5)

SUSE-SU-2025:02391-1
Security update for the Linux Kernel (Live Patch 58 for SLE 12 SP5)

SUSE-SU-2024:3467-1
Security update for the Linux Kernel

SUSE-SU-2025:02416-1
Security update for the Linux Kernel (Live Patch 45 for SLE 15 SP3)

SUSE-SU-2025:02398-1
Security update for the Linux Kernel (Live Patch 46 for SLE 15 SP3)

SUSE-SU-2025:02455-1
Security update for the Linux Kernel (Live Patch 27 for SLE 15 SP4)

SUSE-SU-2025:02436-1
Security update for the Linux Kernel (Live Patch 28 for SLE 15 SP4)

SUSE-SU-2025:02419-1
Security update for the Linux Kernel (Live Patch 29 for SLE 15 SP4)

SUSE-SU-2025:02403-1
Security update for the Linux Kernel (Live Patch 15 for SLE 15 SP5)

SUSE-SU-2025:02440-1
Security update for the Linux Kernel (Live Patch 0 for SLE 15 SP6)

SUSE-SU-2025:02390-1
Security update for the Linux Kernel RT (Live Patch 0 for SLE 15 SP6)

SUSE-SU-2024:3499-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
---|---|---|---|---|
![]() | CVE-2024-42232 In the Linux kernel, the following vulnerability has been resolved: libceph: fix race between delayed_work() and ceph_monc_stop() The way the delayed work is handled in ceph_monc_stop() is prone to races with mon_fault() and possibly also finish_hunting(). Both of these can requeue the delayed work which wouldn't be canceled by any of the following code in case that happens after cancel_delayed_work_sync() runs -- __close_session() doesn't mess with the delayed work in order to avoid interfering with the hunting interval logic. This part was missed in commit b5d91704f53e ("libceph: behave in mon_fault() if cur_mon < 0") and use-after-free can still ensue on monc and objects that hang off of it, with monc->auth and monc->monmap being particularly susceptible to quickly being reused. To fix this: - clear monc->cur_mon and monc->hunting as part of closing the session in ceph_monc_stop() - bail from delayed_work() if monc->cur_mon is cleared, similar to how it's done in mon_fault() an... | CVSS3: 5.5 | 0% Низкий | 12 месяцев назад |
![]() | CVE-2024-42232 In the Linux kernel, the following vulnerability has been resolved: libceph: fix race between delayed_work() and ceph_monc_stop() The way the delayed work is handled in ceph_monc_stop() is prone to races with mon_fault() and possibly also finish_hunting(). Both of these can requeue the delayed work which wouldn't be canceled by any of the following code in case that happens after cancel_delayed_work_sync() runs -- __close_session() doesn't mess with the delayed work in order to avoid interfering with the hunting interval logic. This part was missed in commit b5d91704f53e ("libceph: behave in mon_fault() if cur_mon < 0") and use-after-free can still ensue on monc and objects that hang off of it, with monc->auth and monc->monmap being particularly susceptible to quickly being reused. To fix this: - clear monc->cur_mon and monc->hunting as part of closing the session in ceph_monc_stop() - bail from delayed_work() if monc->cur_mon is cleared, similar to how it's done in mon_fault() an... | CVSS3: 5.5 | 0% Низкий | 12 месяцев назад |
![]() | CVE-2024-42232 In the Linux kernel, the following vulnerability has been resolved: libceph: fix race between delayed_work() and ceph_monc_stop() The way the delayed work is handled in ceph_monc_stop() is prone to races with mon_fault() and possibly also finish_hunting(). Both of these can requeue the delayed work which wouldn't be canceled by any of the following code in case that happens after cancel_delayed_work_sync() runs -- __close_session() doesn't mess with the delayed work in order to avoid interfering with the hunting interval logic. This part was missed in commit b5d91704f53e ("libceph: behave in mon_fault() if cur_mon < 0") and use-after-free can still ensue on monc and objects that hang off of it, with monc->auth and monc->monmap being particularly susceptible to quickly being reused. To fix this: - clear monc->cur_mon and monc->hunting as part of closing the session in ceph_monc_stop() - bail from delayed_work() if monc->cur_mon is cleared, similar to how it's done in mon_fault | CVSS3: 5.5 | 0% Низкий | 12 месяцев назад |
![]() | CVSS3: 5.5 | 0% Низкий | 12 месяцев назад | |
CVE-2024-42232 In the Linux kernel, the following vulnerability has been resolved: l ... | CVSS3: 5.5 | 0% Низкий | 12 месяцев назад | |
GHSA-5vqw-wppf-x433 In the Linux kernel, the following vulnerability has been resolved: libceph: fix race between delayed_work() and ceph_monc_stop() The way the delayed work is handled in ceph_monc_stop() is prone to races with mon_fault() and possibly also finish_hunting(). Both of these can requeue the delayed work which wouldn't be canceled by any of the following code in case that happens after cancel_delayed_work_sync() runs -- __close_session() doesn't mess with the delayed work in order to avoid interfering with the hunting interval logic. This part was missed in commit b5d91704f53e ("libceph: behave in mon_fault() if cur_mon < 0") and use-after-free can still ensue on monc and objects that hang off of it, with monc->auth and monc->monmap being particularly susceptible to quickly being reused. To fix this: - clear monc->cur_mon and monc->hunting as part of closing the session in ceph_monc_stop() - bail from delayed_work() if monc->cur_mon is cleared, similar to how it's done in mon_fa... | CVSS3: 5.5 | 0% Низкий | 12 месяцев назад | |
![]() | BDU:2024-08326 Уязвимость функции ceph_monc_stop() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | около 1 года назад |
![]() | SUSE-SU-2025:02422-1 Security update for the Linux Kernel (Live Patch 57 for SLE 12 SP5) | 14 дней назад | ||
![]() | SUSE-SU-2025:02392-1 Security update for the Linux Kernel (Live Patch 59 for SLE 12 SP5) | 16 дней назад | ||
![]() | SUSE-SU-2025:02391-1 Security update for the Linux Kernel (Live Patch 58 for SLE 12 SP5) | 16 дней назад | ||
![]() | SUSE-SU-2024:3467-1 Security update for the Linux Kernel | 10 месяцев назад | ||
![]() | SUSE-SU-2025:02416-1 Security update for the Linux Kernel (Live Patch 45 for SLE 15 SP3) | 14 дней назад | ||
![]() | SUSE-SU-2025:02398-1 Security update for the Linux Kernel (Live Patch 46 for SLE 15 SP3) | 14 дней назад | ||
![]() | SUSE-SU-2025:02455-1 Security update for the Linux Kernel (Live Patch 27 for SLE 15 SP4) | 14 дней назад | ||
![]() | SUSE-SU-2025:02436-1 Security update for the Linux Kernel (Live Patch 28 for SLE 15 SP4) | 14 дней назад | ||
![]() | SUSE-SU-2025:02419-1 Security update for the Linux Kernel (Live Patch 29 for SLE 15 SP4) | 14 дней назад | ||
![]() | SUSE-SU-2025:02403-1 Security update for the Linux Kernel (Live Patch 15 for SLE 15 SP5) | 14 дней назад | ||
![]() | SUSE-SU-2025:02440-1 Security update for the Linux Kernel (Live Patch 0 for SLE 15 SP6) | 14 дней назад | ||
![]() | SUSE-SU-2025:02390-1 Security update for the Linux Kernel RT (Live Patch 0 for SLE 15 SP6) | 16 дней назад | ||
![]() | SUSE-SU-2024:3499-1 Security update for the Linux Kernel | 10 месяцев назад |
Уязвимостей на страницу