CVE-2024-46740: binder: fix UAF caused by offsets overwrite
In the Linux kernel, the following vulnerability has been resolved:
binder: fix UAF caused by offsets overwrite
Binder objects are processed and copied individually into the target
buffer during transactions. Any raw data in-between these objects is
copied as well. However, this raw data copy lacks an out-of-bounds
check. If the raw data exceeds the data section size then the copy
overwrites the offsets section. This eventually triggers an error that
attempts to unwind the processed objects. However, at this point the
offsets used to index these objects are now corrupted.
Unwinding with corrupted offsets can result in decrements of arbitrary
nodes and lead to their premature release. Other users of such nodes are
left with a dangling pointer triggering a use-after-free. This issue is
made evident by the following KASAN report (trimmed):
==================================================================
BUG: KASAN: slab-use-after-free in _raw_spin_lock+0xe4/0x19c
Write of size 4 at addr ffff47fc91598f04 by task binder-util/743
CPU: 9 UID: 0 PID: 743 Comm: binder-util Not tainted 6.11.0-rc4 #1
Hardware name: linux,dummy-virt (DT)
Call trace:
_raw_spin_lock+0xe4/0x19c
binder_free_buf+0x128/0x434
binder_thread_write+0x8a4/0x3260
binder_ioctl+0x18f0/0x258c
[...]
Allocated by task 743:
__kmalloc_cache_noprof+0x110/0x270
binder_new_node+0x50/0x700
binder_transaction+0x413c/0x6da8
binder_thread_write+0x978/0x3260
binder_ioctl+0x18f0/0x258c
[...]
Freed by task 745:
kfree+0xbc/0x208
binder_thread_read+0x1c5c/0x37d4
binder_ioctl+0x16d8/0x258c
[...]
==================================================================
To avoid this issue, let's check that the raw data copy is within the
boundaries of the data section.
Security readout for executives and security teams
Plain-English summary
CVE-2024-46740 is a Linux kernel Binder flaw that can let a local low-privileged user corrupt kernel object handling and trigger use-after-free behavior. The CVSS score is 7.8 because successful exploitation could affect confidentiality, integrity, and availability. The sources do not show active exploitation or KEV listing.
Executive priority
Treat this as a high-priority kernel maintenance item, especially for shared systems or platforms allowing local untrusted code. There is no sourced evidence of active exploitation, but the impact is broad if exploitation succeeds. Patch through normal emergency or accelerated kernel update channels based on local exposure.
Technical view
Binder transaction processing copies raw data between objects without a bounds check. Oversized raw data can overwrite the offsets section, corrupt unwind indexes, decrement arbitrary Binder nodes, and prematurely free objects still in use. The kernel fix adds a boundary check so raw data copying stays within the data section.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions or vendor kernels that include the vulnerable Binder code. The attack vector is local, requires low privileges, and needs no user interaction. Systems without Binder enabled or reachable by local untrusted users are likely lower exposure, but the source data does not define configuration scope.
Exploitation context
The CVE record gives CVSS AV:L/PR:L/UI:N and CWE-416. It includes a KASAN use-after-free report but no public exploit confirmation. CISA KEV status in the bundle is false, so active exploitation should not be assumed from these sources.
Researcher notes
The core bug is an unchecked raw data copy in Binder transaction handling that corrupts offsets used during error unwinding. The resulting arbitrary node decrements can create dangling pointers. Source evidence supports a local privilege-context memory safety issue, but does not provide exploitability details beyond KASAN evidence and CVSS scoring.
Mitigation direction
Update to a kernel containing the referenced stable Binder fixes.
Apply relevant Debian LTS kernel updates if running Debian.
For vendor kernels, request the vendor backport status for CVE-2024-46740.
Prioritize systems where untrusted local users or workloads can access Binder.
Monitor the CVE record and kernel stable updates for branch-specific guidance.
Validation and detection
Inventory running kernel versions across Linux assets.
Check whether each kernel includes the referenced Binder stable commit for its branch.
Confirm whether Binder is enabled or exposed on higher-risk systems.
Review distro advisories, especially Debian LTS notices, for package-level fix status.
Look for kernel crash telemetry consistent with Binder 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.
1CVSS vectors
3Timeline events
2ADP 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.