CVE-2024-42232: libceph: fix race between delayed_work() and ceph_monc_stop()

Published Aug 7, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

libceph: fix race between delayedwork() and cephmoncstop()

The way the delayed work is handled in cephmoncstop() is prone to races with monfault() and possibly also finishhunting(). Both of these can requeue the delayed work which wouldn't be canceled by any of the following code in case that happens after canceldelayedworksync() runs -- closesession() 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 monfault() if curmon < 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->curmon and monc->hunting as part of closing the session in cephmoncstop() - bail from delayedwork() if monc->curmon is cleared, similar to how it's done in monfault() and finishhunting() (based on monc->hunting) - call canceldelayedworksync() after the session is closed

Affected Software

14 affected componentsFixes available
Linux Linux kernel<4.19.318
Linux Linux kernel>=4.20<5.4.280
Linux Linux kernel>=5.5<5.10.222
Linux Linux kernel>=5.11<5.15.163
Linux Linux kernel>=5.16<6.1.100
Linux Linux kernel>=6.2<6.6.41
Linux Linux kernel>=6.7<6.9.10
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1
Microsoft azl3 kernel 6.6.43.1-7
Microsoft cbl2 kernel 5.15.162.2-1
Microsoft cbl2 kernel 5.15.162.2-1
Microsoft azl3 kernel 6.6.35.1-5
Microsoft cbl2 kernel 5.15.164.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1
  2. Upgrade

    Upgrade debian/linux-6.1 to a version that resolves this vulnerability.

    Fixed in 6.1.129-1~deb11u1
  3. Configuration

    In ceph_monc_stop(), implement the described fix: (1) clear monc->cur_mon and monc->hunting during session close, (2) in delayed_work(), bail out if monc->cur_mon is cleared (similar to mon_fault() / finish_hunting()), and (3) call cancel_delayed_work_sync() after the session is closed to prevent delayed work from requeuing after cancellation.

    Linux kernel (libceph) ceph_monc_stop() delayed work shutdown logic = clear monc->cur_mon and monc->hunting as part of closing the session; bail from delayed_work() when monc->cur_mon is cleared; call cancel_delayed_work_sync() after the session is closed

Event History

Aug 7, 2024
CVE Published
via MITRE·03:14 PM
Data Sourced
via MITRE·03:14 PM
DescriptionSeverity
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 16, 2024
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
SeverityAffected Software
Updated
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
May 3, 2025
Data Sourced
via Ubuntu·06:22 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-42232?

CVE-2024-42232 has a high severity due to its potential impact on the stability of the Linux kernel.

2

How do I fix CVE-2024-42232?

To fix CVE-2024-42232, upgrade the Linux kernel to a version that is patched against this vulnerability.

3

Which versions of the Linux kernel are affected by CVE-2024-42232?

CVE-2024-42232 affects multiple Linux kernel versions including those between 4.20 and 5.4.280, and others up to 6.9.10.

4

What components are involved in the CVE-2024-42232 vulnerability?

The CVE-2024-42232 vulnerability involves a race condition between delayed work and ceph_monc_stop() in the Linux kernel.

5

Is there an exploit available for CVE-2024-42232?

As of now, there is no public proof of concept or exploit for CVE-2024-42232, but it is recommended to apply mitigations.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203