First published: Wed Sep 18 2024(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | >=5.4.226<5.4.284 | |
Linux Kernel | >=5.10.157<5.10.226 | |
Linux Kernel | >=5.15.17<5.15.167 | |
Linux Kernel | >=5.17<6.1.110 | |
Linux Kernel | >=6.2<6.6.51 | |
Linux Kernel | >=6.7<6.10.10 | |
Linux Kernel | =6.11-rc1 | |
Linux Kernel | =6.11-rc2 | |
Linux Kernel | =6.11-rc3 | |
Linux Kernel | =6.11-rc4 | |
Linux Kernel | =6.11-rc5 | |
Linux Kernel | =6.11-rc6 | |
Android | ||
debian/linux | <=5.10.223-1 | 5.10.234-1 6.1.129-1 6.1.135-1 6.12.22-1 6.12.25-1 |
debian/linux-6.1 | 6.1.129-1~deb11u1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-46740 has a high severity rating due to the potential for user-after-free (UAF) vulnerabilities that can be exploited.
To mitigate CVE-2024-46740, update your Linux kernel to a patched version such as 5.10.226 or higher, depending on your specific distribution.
CVE-2024-46740 affects multiple versions of the Linux kernel, specifically those between 5.4.226 and 6.11-rc6.
Exploitation of CVE-2024-46740 could lead to arbitrary code execution or potentially escalate user privileges.
Yes, CVE-2024-46740 affects Google Android due to its reliance on the underlying Linux kernel.