CVE-2024-42232

Advisory lineage Upstream: 0 Downstream: 57
Modified
Published: 07 Aug 2024, 15:14
Last modified:11 May 2026, 20:28

Vulnerability Summary

Overall Risk (default)
low
22/100
CVSS Score
5.5 MEDIUM
v3.1 (nvd)
EPSS Score
0.02% LOW
0% probability 0.00%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

07 Aug 2024, 15:14
Published
Vulnerability first disclosed
11 May 2026, 20:28
Last Modified
Vulnerability information updated

Description

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() and finish_hunting() (based on monc->hunting) - call cancel_delayed_work_sync() after the session is closed

CVSS Metrics

  • v3.1•MEDIUM•Score: 5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS Trends

Current EPSS score: 0.02%• Percentile: 5%

Techniques & Countermeasures

  • CWE-416•Use After Free

    The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Affected Systems

  • linux•linux

    ≥ 0e04dc26cc594d31ee6b1382b452b6bc83b57937, < 1177afeca833174ba83504688eec898c6214f4bf | ≥ 0e04dc26cc594d31ee6b1382b452b6bc83b57937, < 63e5d035e3a7ab7412a008f202633c5e6a0a28ea | ≥ 0e04dc26cc594d31ee6b1382b452b6bc83b57937, < 34b76d1922e41da1fa73d43b764cddd82ac9733c | ≥ 0e04dc26cc594d31ee6b1382b452b6bc83b57937, < 20cf67dcb7db842f941eff1af6ee5e9dc41796d7 | ≥ 0e04dc26cc594d31ee6b1382b452b6bc83b57937, < 2d33654d40a05afd91ab24c9a73ab512a0670a9a | ≥ 0e04dc26cc594d31ee6b1382b452b6bc83b57937, < 9525af1f58f67df387768770fcf6d6a8f23aee3d | ≥ 0e04dc26cc594d31ee6b1382b452b6bc83b57937, < 33d38c5da17f8db2d80e811b7829d2822c10625e | ≥ 0e04dc26cc594d31ee6b1382b452b6bc83b57937, < 69c7b2fe4c9cc1d3b1186d1c5606627ecf0de883 | 4.6

  • linux•linux_kernel

    < 4.19.318 | ≥ 4.20, < 5.4.280 | ≥ 5.5, < 5.10.222 | ≥ 5.11, < 5.15.163 | ≥ 5.16, < 6.1.100 | ≥ 6.2, < 6.6.41 | ≥ 6.7, < 6.9.10

References (9)