CyberSecBulletin
CVE-2026-64469NVD status: Undergoing Analysis

Linux: Use After Free

Published Updated By the CyberSecBulletin desk

CVE-2026-64469 is a high-severity use after free vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 1f96f8c0a6ed4f6d01d3dd29ad0cbf08dde96082, df1a17abba8d6fac5f965adcb8113ceace6e4949, 38e1a71728e5795b670cc159c18e286a40aeebb4 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.14% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 1f96f8c0a6ed4f6d01d3dd29ad0cbf08dde96082 or df1a17abba8d6fac5f965adcb8113ceace6e4949 or 38e1a71728e5795b670cc159c18e286a40aeebb4 or faa070c7ad8ba25dcd0b12d7cdbb419e336f5391, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.10.261 or 5.15.212 or 6.1.178 or 6.6.145, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux7a4408c6bd3eb1dafba67986259191be081e3efb up to, but not including, 1f96f8c0a6ed4f6d01d3dd29ad0cbf08dde96082; 7a4408c6bd3eb1dafba67986259191be081e3efb up to, but not including, df1a17abba8d6fac5f965adcb8113ceace6e4949; 7a4408c6bd3eb1dafba67986259191be081e3efb up to, but not including, 38e1a71728e5795b670cc159c18e286a40aeebb4; 7a4408c6bd3eb1dafba67986259191be081e3efb up to, but not including, faa070c7ad8ba25dcd0b12d7cdbb419e336f5391; 7a4408c6bd3eb1dafba67986259191be081e3efb up to, but not including, e63032dc715026a96bcaa13d375a8e15c91caa84; 7a4408c6bd3eb1dafba67986259191be081e3efb up to, but not including, ea02df466df60ecd758eb3b4df3f0cadc5c886ce; 7a4408c6bd3eb1dafba67986259191be081e3efb up to, but not including, ef5439ba5b9ac93349f5df12ef88b42a0ce26340; 7a4408c6bd3eb1dafba67986259191be081e3efb up to, but not including, 114a116aaa5f0295376cdf12da743c5bce3b20ce; and 1 more ranges1f96f8c0a6ed4f6d01d3dd29ad0cbf08dde96082, df1a17abba8d6fac5f965adcb8113ceace6e4949, 38e1a71728e5795b670cc159c18e286a40aeebb4, faa070c7ad8ba25dcd0b12d7cdbb419e336f5391, e63032dc715026a96bcaa13d375a8e15c91caa84, ea02df466df60ecd758eb3b4df3f0cadc5c886ce
LinuxLinux Kernel4.14 up to, but not including, 5.10.261; 5.11 up to, but not including, 5.15.212; 5.16 up to, but not including, 6.1.178; 6.2 up to, but not including, 6.6.145; 6.7 up to, but not including, 6.12.96; 6.13 up to, but not including, 6.18.39; 6.19 up to, but not including, 7.1.4; 7.25.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, 6.18.39

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.

Official description

In the Linux kernel, the following vulnerability has been resolved: binder: fix UAF in binder_thread_release() When a thread exits, binder_thread_release() walks its transaction stack to clear the t->from and t->to_proc that correspond with the exiting thread. However, a process dying in parallel might attempt to kfree some of these transactions. And if one of them has no associated t->to_proc, the t->to_proc->inner_lock will not be acquired. This means that transaction accesses in binder_thread_release() after t->to_proc has been cleared might race with binder_free_transaction() and cause a use-after-free error as reported by KASAN: ================================================================== BUG: KASAN: slab-use-after-free in binder_thread_release+0x5d0/0x798 Write of size 8 at addr ffff000016627500 by task X/715 CPU: 17 UID: 0 PID: 715 Comm: X Not tainted 7.1.0-rc5-00149-g8fde5d1d47f6 #30 PREEMPT Hardware name: linux,dummy-virt (DT) Call trace: binder_thread_release+0x5d0/0x798 binder_ioctl+0x12c0/0x299c [...] Allocated by task 717 on cpu 18 at 67.267803s: __kasan_kmalloc+0xa0/0xbc __kmalloc_cache_noprof+0x174/0x444 binder_transaction+0x554/0x8150 binder_thread_write+0xa30/0x4354 binder_ioctl+0x20f0/0x299c [...] Freed by task 202 on cpu 18 at 90.416221s: __kasan_slab_free+0x58/0x80 kfree+0x1a0/0x4a4 binder_free_transaction+0x150/0x294 binder_send_failed_reply+0x398/0x6d8 binder_release_work+0x3e4/0x4ec binder_deferred_func+0xbd8/0x104c [...] ================================================================== In order to avoid this, make sure that binder_free_transaction() reads the t->to_proc under the transaction lock. This will serialize the transaction release with the accesses in binder_thread_release(). Plus, it matches the documented locking rules for @to_proc.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Use After Free

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

How developers prevent this class of flaw

  • Choose a language that provides automatic memory management.
  • When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.

More Use After Free vulnerabilities (CWE-416)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Recent Use After Free vulnerabilities

Spotted an error? Tell us.