CVE-2024-46740
binder: fix UAF caused by offsets overwrite
Reported by linux · Published September 18, 2024
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| linux_kernel | linux | 6.10.10, 6.6.51, 6.1.110, 5.15.167, 5.10.226, 5.4.284 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | c056a6ba35e00ae943e377eb09abd77a6915b31a, 23e9d815fad84c1bee3742a8de4bd39510435362, 7a9ad4aceb0226b391c9d3b8e4ac2e7d438b6bde |
| Linux | Linux | 5.17, 0, 5.4.284 |
| linux | linux_kernel | 5.10.157, 5.17, 5.17 |
| Linux | Linux | 7a9ad4aceb0226b391c9d3b8e4ac2e7d438b6bde, 6d98eb95b450a75adb4516a1d33652dc78d2b20c, 6d98eb95b450a75adb4516a1d33652dc78d2b20c |
Timeline
- Sep 17, 2024 CVE Published
- Sep 19, 2024 EPSS Score (30 in total, the first dated here)
- Oct 5, 2024 Coalition ESS Score (17 in total, the first dated here)
- Jan 4, 2026 Security Advisory (160 in total, the first dated here)
- Jan 4, 2026 CVE Updated
- Mar 30, 2026 Distribution Patch (146 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2024-46740
vulnetix vdb fixes CVE-2024-46740
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-46740/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart