CVE-2024-56554: binder: fix freeze UAF in binder_release_work()
In the Linux kernel, the following vulnerability has been resolved:
binder: fix freeze UAF in binder_release_work()
When a binder reference is cleaned up, any freeze work queued in the
associated process should also be removed. Otherwise, the reference is
freed while its ref->freeze.work is still queued in proc->work leading
to a use-after-free issue as shown by the following KASAN report:
==================================================================
BUG: KASAN: slab-use-after-free in binder_release_work+0x398/0x3d0
Read of size 8 at addr ffff31600ee91488 by task kworker/5:1/211
CPU: 5 UID: 0 PID: 211 Comm: kworker/5:1 Not tainted 6.11.0-rc7-00382-gfc6c92196396 #22
Hardware name: linux,dummy-virt (DT)
Workqueue: events binder_deferred_func
Call trace:
binder_release_work+0x398/0x3d0
binder_deferred_func+0xb60/0x109c
process_one_work+0x51c/0xbd4
worker_thread+0x608/0xee8
Allocated by task 703:
__kmalloc_cache_noprof+0x130/0x280
binder_thread_write+0xdb4/0x42a0
binder_ioctl+0x18f0/0x25ac
__arm64_sys_ioctl+0x124/0x190
invoke_syscall+0x6c/0x254
Freed by task 211:
kfree+0xc4/0x230
binder_deferred_func+0xae8/0x109c
process_one_work+0x51c/0xbd4
worker_thread+0x608/0xee8
==================================================================
This commit fixes the issue by ensuring any queued freeze work is removed
when cleaning up a binder reference.
Security readout for executives and security teams
Plain-English summary
A Linux Binder cleanup flaw can leave queued work pointing to freed memory. A local, low-privileged user could potentially trigger memory corruption, causing system compromise or disruption. The supplied CVSS score is 7.8 (High), but the sources do not establish real-world exploitation.
Executive priority
Treat as a high-priority local privilege and stability risk, especially where untrusted users or applications can access Binder. Patch during the next expedited maintenance cycle. Escalate systems with broad local access, while recognizing that the supplied evidence does not show active exploitation.
Technical view
CVE-2024-56554 is a CWE-416 use-after-free in binder_release_work(). Binder reference cleanup could free a reference without removing its queued freeze work from the process work list. Later worker processing could access the freed object. The cited fix removes queued freeze work during reference cleanup.
Likely exposure
Exposure requires a vulnerable Linux kernel containing the affected Binder code and local low-privileged access. The supplied version data references 6.12, 6.12.4, and 6.13 but is ambiguous; verify each distribution kernel by backport status rather than version alone.
Exploitation context
The CVSS vector indicates local access, low complexity, low privileges, and no user interaction, with potentially high confidentiality, integrity, and availability impact. This CVE is not listed as KEV in the supplied bundle, and no cited source confirms active exploitation or a public weaponized exploit.
Researcher notes
The source includes a KASAN slab-use-after-free report from deferred Binder work on arm64. Root cause and repair are narrowly described: remove freeze work queued on proc->work when releasing its Binder reference. Exact affected release boundaries and exploitability beyond the demonstrated memory error are not fully established in the bundle.
Mitigation direction
Install a vendor-supported kernel update containing the cited Binder cleanup fix.
Confirm the update applies to the running kernel, including distribution-specific backports.
Restrict unnecessary local account and application access until affected systems are updated.
Prioritize Binder-enabled multi-user or untrusted-application systems for remediation.
Validation and detection
Inventory running kernel builds on systems where Linux Binder is enabled or used.
Check vendor advisories or kernel changelogs for either cited fix commit or an equivalent backport.
Verify the patched kernel is running after maintenance, not merely installed.
Review kernel crash and memory-safety telemetry for Binder-related use-after-free symptoms.
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
3Source 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.