CVE-2024-41149: block: avoid to reuse `hctx` not removed from cpuhp callback list
In the Linux kernel, the following vulnerability has been resolved:
block: avoid to reuse `hctx` not removed from cpuhp callback list
If the 'hctx' isn't removed from cpuhp callback list, we can't reuse it,
otherwise use-after-free may be triggered.
Security readout for executives and security teams
Plain-English summary
A Linux block-layer flaw can leave a hardware-queue context registered for CPU-hotplug callbacks and later reuse freed memory. A local, low-privileged user may be able to cause a kernel crash or compromise. The supplied CVSS score is 7.8 (High), but the affected-version boundaries are unclear.
Executive priority
Treat this as expedited kernel maintenance, prioritizing shared or multi-user Linux systems and hosts allowing untrusted local access. It is high severity because successful exploitation could affect all three security properties, but the supplied evidence does not justify claiming an active-exploitation emergency.
Technical view
CVE-2024-41149 is a CWE-416 use-after-free involving reuse of an hctx that was not removed from the CPU-hotplug callback list. Its CVSS vector indicates local access, low complexity, low privileges, no user interaction, and potentially high confidentiality, integrity, and availability impact.
Likely exposure
Potential exposure exists on Linux systems running the vulnerable block-layer code where an attacker has local, low-privileged access. The sources do not describe a remote attack path. The bundle marks its listed commits and Linux 6.12.6 as unaffected, without supplying a conventional affected-version range.
Exploitation context
The supplied record is not in CISA KEV, and the sources provide no evidence of active exploitation. Exploitation requires local, low-privileged access according to the CVSS vector. Lack of reported exploitation does not establish that exploitation is impossible.
Researcher notes
The record attributes the flaw to hctx lifecycle handling around the CPU-hotplug callback list and supplies three Linux stable commit references. It does not clearly identify introduced versions or a complete affected range. Distribution backports may make upstream version comparisons unreliable; vendor-specific package status is needed.
Mitigation direction
Check distribution and kernel-vendor advisories for exact affected builds and supported fixes.
Upgrade to a vendor-supported kernel containing the applicable stable correction.
Until updated, reduce untrusted local account access where operationally feasible.
Reboot affected systems into the corrected kernel following normal change controls.
Validation and detection
Inventory running kernel versions across Linux servers, workstations, appliances, and virtual machines.
Map distribution builds to vendor advisories instead of relying only on upstream version numbers.
Confirm each updated kernel contains the vendor-designated correction for CVE-2024-41149.
Verify rebooted systems are actually running the corrected kernel.
Review kernel crash records for relevant block-layer or CPU-hotplug failures.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.