Skip to content
Fencer Intel
critical 9.8

CVE-2024-42232 in the critical feed json

libceph: fix race between delayed_work() and ceph_monc_stop()

published 2y ago modified 3mo ago also EUVD-2024-39884

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits
0
none known

Summary

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

Patch / fix

  • Linux Linux 4.19.318, 5.4.280, 5.10.222, 5.15.163, 6.1.100, 6.6.41, 6.9.10, 6.10
  • linux Debian 12 6.1.106-1
  • linux Debian 14, Debian 13 6.9.10-1

debian advisories DEBIAN-CVE-2024-42232

  • linux Ubuntu 20.04 LTS 5.4.0-195.215
  • linux Ubuntu 22.04 LTS 5.15.0-121.131
  • linux Ubuntu 24.04 LTS 6.8.0-48.48
  • linux-aws Ubuntu 20.04 LTS 5.4.0-1132.142
  • linux-aws Ubuntu 22.04 LTS 5.15.0-1069.75
  • linux-aws Ubuntu 24.04 LTS 6.8.0-1018.20
  • linux-gcp Ubuntu 20.04 LTS 5.4.0-1136.145
  • linux-gcp Ubuntu 22.04 LTS 5.15.0-1068.76

ubuntu advisories UBUNTU-CVE-2024-42232

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-64kb SLE High Performance Computing 15 SP5-ESPOS, SLES 15 SP5-LTSS, SLE High Performance Computing 15 SP5-LTSS 5.14.21-150500.55.91.1
  • kernel-syms SLE High Performance Computing 15 SP5-ESPOS, SLES for SAP 15 SP5, SLES 15 SP5-LTSS +1 more 5.14.21-150500.55.91.1
  • kernel-source SLE High Performance Computing 15 SP5-ESPOS, SLES for SAP 15 SP5, SLES 15 SP5-LTSS +1 more 5.14.21-150500.55.91.1
  • kernel-default SLE Micro 5.5, SLE High Performance Computing 15 SP5-ESPOS, SLES for SAP 15 SP5 +3 more 5.14.21-150500.55.91.1
  • kernel-obs-build SLE High Performance Computing 15 SP5-ESPOS, SLES for SAP 15 SP5, SLES 15 SP5-LTSS +1 more 5.14.21-150500.55.91.1
  • kernel-default-base SLE Micro 5.5, SLE High Performance Computing 15 SP5-ESPOS, SLES for SAP 15 SP5 +2 more 5.14.21-150500.55.91.1.150500.6.41.1
  • kernel-rt Linux Micro 6.0 6.4.0-10.1
  • kernel-source-rt Linux Micro 6.0 6.4.0-10.1

suse advisories SUSE-SU-2025:02455-1SUSE-SU-2025:02436-1SUSE-SU-2025:02440-1SUSE-SU-2025:02422-1SUSE-SU-2025:02419-1SUSE-SU-2025:02416-1

  • kernel Azure Linux 3.0 6.6.43.1-7
  • kernel CBL-Mariner 2.0 5.15.164.1-1

azure linux advisories AZL-47561AZL-47624

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2024-42232 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-42232 updated cvss 5.5

kernel: libceph: fix race between delayed_work() and ceph_monc_stop()

  • Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

cisa ICSA-25-226-07 updated

Siemens Third-Party Components in SINEC OS

  • Siemens RUGGEDCOM RST2428P (6GK6242-6PA00) Siemens SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family Siemens SCALANCE XCM-/XRM-/XCH-/XRH-300 family
    not affected

Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf

cisa ICSA-25-226-15 updated cvss 5.5

Siemens SINEC OS

  • Siemens RUGGEDCOM RST2428P (6GK6242-6PA00) < 3.1 Siemens SCALANCE XCM-/XRM-/XCH-/XRH-300 family < 3.1
    affected: fixed in V3.1 support.industry.siemens.com
  • Siemens SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
    not affected

Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.76% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.