CVE-2024-38384: blk-cgroup: fix list corruption from reorder of WRITE ->lqueued
In the Linux kernel, the following vulnerability has been resolved:
blk-cgroup: fix list corruption from reorder of WRITE ->lqueued
__blkcg_rstat_flush() can be run anytime, especially when blk_cgroup_bio_start
is being executed.
If WRITE of `->lqueued` is re-ordered with READ of 'bisc->lnode.next' in
the loop of __blkcg_rstat_flush(), `next_bisc` can be assigned with one
stat instance being added in blk_cgroup_bio_start(), then the local
list in __blkcg_rstat_flush() could be corrupted.
Fix the issue by adding one barrier.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel flaw in block cgroup accounting. A timing issue can corrupt an internal list while I/O statistics are being updated. The CVE rates impact as high because successful triggering could affect confidentiality, integrity, and availability on the local system.
Executive priority
Treat this as a high-priority Linux maintenance item for shared or production infrastructure. There is no source-backed evidence of active exploitation, but the kernel-level impact and no-privilege local vector justify timely patch validation.
Technical view
The bug is in blk-cgroup rstat flushing. A reordered write to ->lqueued versus a read of bisc->lnode.next can let __blkcg_rstat_flush() see an entry concurrently added by blk_cgroup_bio_start(), corrupting the local list. Upstream stable commits add a memory barrier.
Likely exposure
Exposure is most relevant to Linux systems running affected kernels with block cgroup functionality in use, especially multi-user, containerized, or workload-isolated hosts. The source bundle does not identify affected distributions or cloud images.
Exploitation context
The CVSS vector is local, low complexity, no privileges, and no user interaction. The bundle says KEV is false and provides no cited evidence of active exploitation or public exploit availability.
Researcher notes
The evidence points to a concurrency and memory-ordering defect in blk-cgroup accounting, fixed by a barrier. Source data is incomplete for distribution package status, exploitability constraints, and operational mitigations beyond applying fixed kernels.
Mitigation direction
Update Linux kernels using vendor packages that include the referenced upstream stable fixes.
Check distribution advisories for exact fixed package versions and reboot requirements.
Prioritize shared hosts, container platforms, and systems using cgroup-based workload isolation.
If immediate patching is delayed, follow vendor guidance for risk reduction.
Validation and detection
Inventory Linux kernel versions across servers, containers hosts, and appliances.
Map deployed kernels to vendor advisories for CVE-2024-38384.
Confirm updated kernels include one of the referenced stable commits or vendor backports.
After patching, verify systems are rebooted into the corrected kernel.
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-400: 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.
1CVSS vectors
3Timeline events
2ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
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-400 · source CWE mapping
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.