CVE-2024-56672: blk-cgroup: Fix UAF in blkcg_unpin_online()
In the Linux kernel, the following vulnerability has been resolved:
blk-cgroup: Fix UAF in blkcg_unpin_online()
blkcg_unpin_online() walks up the blkcg hierarchy putting the online pin. To
walk up, it uses blkcg_parent(blkcg) but it was calling that after
blkcg_destroy_blkgs(blkcg) which could free the blkcg, leading to the
following UAF:
==================================================================
BUG: KASAN: slab-use-after-free in blkcg_unpin_online+0x15a/0x270
Read of size 8 at addr ffff8881057678c0 by task kworker/9:1/117
CPU: 9 UID: 0 PID: 117 Comm: kworker/9:1 Not tainted 6.13.0-rc1-work-00182-gb8f52214c61a-dirty #48
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS unknown 02/02/2022
Workqueue: cgwb_release cgwb_release_workfn
Call Trace:
<TASK>
dump_stack_lvl+0x27/0x80
print_report+0x151/0x710
kasan_report+0xc0/0x100
blkcg_unpin_online+0x15a/0x270
cgwb_release_workfn+0x194/0x480
process_scheduled_works+0x71b/0xe20
worker_thread+0x82a/0xbd0
kthread+0x242/0x2c0
ret_from_fork+0x33/0x70
ret_from_fork_asm+0x1a/0x30
</TASK>
...
Freed by task 1944:
kasan_save_track+0x2b/0x70
kasan_save_free_info+0x3c/0x50
__kasan_slab_free+0x33/0x50
kfree+0x10c/0x330
css_free_rwork_fn+0xe6/0xb30
process_scheduled_works+0x71b/0xe20
worker_thread+0x82a/0xbd0
kthread+0x242/0x2c0
ret_from_fork+0x33/0x70
ret_from_fork_asm+0x1a/0x30
Note that the UAF is not easy to trigger as the free path is indirected
behind a couple RCU grace periods and a work item execution. I could only
trigger it with artifical msleep() injected in blkcg_unpin_online().
Fix it by reading the parent pointer before destroying the blkcg's blkg's.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory-safety flaw in block cgroup cleanup. A local low-privileged user could potentially cause serious confidentiality, integrity, or availability impact. The source says the bug was difficult to trigger in testing, but the CVSS score is high.
Executive priority
Patch during the next high-priority kernel maintenance window, sooner for shared or untrusted workload hosts. No active exploitation is evidenced here, but the potential impact is high.
Technical view
blkcg_unpin_online() could read a block cgroup parent pointer after blkcg_destroy_blkgs() potentially freed the object, causing a use-after-free. The fix reads the parent pointer before destroying the blkcg block groups. The issue is CWE-416 with CVSS 3.1 score 7.8.
Likely exposure
Exposure is limited to Linux systems running affected kernel versions or downstream products that include the vulnerable blk-cgroup code. Risk is most relevant where local users, workloads, or hosted services can execute code on the system.
Exploitation context
The bundle does not show KEV listing or active exploitation. The kernel description says triggering was not easy and required artificial delay injection during testing. Treat exploitability as plausible but not confirmed in the provided sources.
Researcher notes
The strongest evidence is the upstream kernel fix narrative and stable commit references. The provided affected-version data is incomplete in this prompt, so use vendor advisories for exact package and product applicability.
Mitigation direction
Update to a vendor kernel containing the referenced stable fixes.
Prioritize multi-user Linux hosts and systems running untrusted workloads.
Check Debian LTS and Siemens advisories if those environments apply.
Follow distribution or vendor guidance for exact package versions.
Plan reboot or live-patching according to normal kernel update process.
Validation and detection
Inventory Linux kernel versions across affected servers and appliances.
Map kernels against vendor advisories and referenced stable commits.
Confirm whether Debian LTS or Siemens-covered products are in scope.
Verify patched systems are running the updated kernel after maintenance.
Monitor kernel logs for instability, but do not rely on logs for exposure proof.
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.
1CVSS vectors
3Timeline events
3ADP providers
10Source 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-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.