CVE-2026-64468

CVE CVE-2026-64468EUVD EUVD-2026-48812Published 2026-07-25T08:51:33.000ZLast changed 2026-08-05T12:42:21.000ZCVSS 7.8

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: binder: fix UAF in binder_free_transaction() In binder_free_transaction(), the t->to_proc is read under the t->lock. However, once the t->lock is dropped, the to_proc can die in parallel. This leads to a use-after-free error when we attempt to acquire its inner lock right afterwards: ================================================================== BUG: KASAN: slab-use-after-free in _raw_spin_lock+0xe4/0x1a0 Write of size 4 at addr ffff00001125da70 by task B/672 CPU: 20 UID: 0 PID: 672 Comm: B Not tainted 7.1.0-rc6-00284-g8e65320d91cd #4 PREEMPT Hardware name: linux,dummy-virt (DT) Call trace: _raw_spin_lock+0xe4/0x1a0 binder_free_transaction+0x8c/0x320 binder_send_failed_reply+0x21c/0x2f8 binder_thread_release+0x488/0x7e0 binder_ioctl+0x12c0/0x29a0 [...] Allocated by task 675: __kmalloc_cache_noprof+0x174/0x444 binder_open+0x118/0xb70 do_dentry_open+0x374/0x1040 vfs_open+0x58/0x3bc [...] Freed by task 212: __kasan_slab_free+0x58/0x80 kfree+0x1a0/0x4a4 binder_proc_dec_tmpref+0x32c/0x5e0 binder_deferred_func+0xc48/0x104c process_one_work+0x53c/0xbc0 [...] ================================================================== To prevent this, pin the target thread (t->to_thread) to guarantee the target process remains alive. Undelivered transactions without a target thread are already safe, as the target process can only be the current context in those paths.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux a4a3c070b8760f71c8311399fa9bfe67c8629bca; 0e3b977a8f1be01dcfa0baae68851b1f55f2a0a9; patch: 6.12.96; patch: 7.2-rc3; patch: 5.15.212; patch: 5.10.261; 4.19.64 <4.20; a370003cc301d4361bae20c9ef615f89bf8d1e8a <45df558c543bb5543bacc8065fd7c567740781e5; patch: 6.6.145; 22068d49d09d2b3890e19d7b2048a33340f992da; a370003cc301d4361bae20c9ef615f89bf8d1e8a <5602a43f251c3d75312df91a422675fc00ca3dce; patch: 6.1.178; a370003cc301d4361bae20c9ef615f89bf8d1e8a <0be901ab1dcc4af59b88f2e324493bb283850167; 5.1.15 <5.2; patch: 6.18.39; a370003cc301d4361bae20c9ef615f89bf8d1e8a <f223d27a546c1e1f48d38fd67760e78f068fe8c4; a370003cc301d4361bae20c9ef615f89bf8d1e8a <0f15f0f6ca5df566275ce517f257af2559528b41; a370003cc301d4361bae20c9ef615f89bf8d1e8a <d45ef513eed1abebfec90c3cfb6ae50c2a4182db; a370003cc301d4361bae20c9ef615f89bf8d1e8a <48aeda9f8039e4a6971d1804578efde7f2c01eda; 5.2; patch: 0; patch: 7.1.4; 4.14.136 <4.15; a370003cc301d4361bae20c9ef615f89bf8d1e8a <328ccf32acb87e8bbb1fe2b065068c574e4db2bf

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.