Linux: Use After Free
CVE-2026-64470 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 1edd524de5cc8143ece9c42c466346983dc5b5ed, 0ccb1cb0a464dab78284c34196cd3e8e18bab4c4, 631de465aba7f8ae46478bf5f598111412e8eff8 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.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to 1edd524de5cc8143ece9c42c466346983dc5b5ed or 0ccb1cb0a464dab78284c34196cd3e8e18bab4c4 or 631de465aba7f8ae46478bf5f598111412e8eff8 or 6e1b10df890f4663cb38af9fc1c93d36747b75af, whichever matches your release line, or a later version.
- 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
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | a4ccc9e33d2f01532bcceb621ea06bbf4db6efac up to, but not including, 1edd524de5cc8143ece9c42c466346983dc5b5ed; a4ccc9e33d2f01532bcceb621ea06bbf4db6efac up to, but not including, 0ccb1cb0a464dab78284c34196cd3e8e18bab4c4; a4ccc9e33d2f01532bcceb621ea06bbf4db6efac up to, but not including, 631de465aba7f8ae46478bf5f598111412e8eff8; a4ccc9e33d2f01532bcceb621ea06bbf4db6efac up to, but not including, 6e1b10df890f4663cb38af9fc1c93d36747b75af; a4ccc9e33d2f01532bcceb621ea06bbf4db6efac up to, but not including, 92c736866244340497a8a65afe2ac25354c2bf5e; a4ccc9e33d2f01532bcceb621ea06bbf4db6efac up to, but not including, a7e941a395711791c7e98d9870c6562c2c9e9ef2; a4ccc9e33d2f01532bcceb621ea06bbf4db6efac up to, but not including, 838c917a2f16eefe68def800ebf48a2af591149a; a4ccc9e33d2f01532bcceb621ea06bbf4db6efac up to, but not including, c5b600a3c05b1a7a110d558df935a8fc8a471c79; and 1 more ranges | 1edd524de5cc8143ece9c42c466346983dc5b5ed, 0ccb1cb0a464dab78284c34196cd3e8e18bab4c4, 631de465aba7f8ae46478bf5f598111412e8eff8, 6e1b10df890f4663cb38af9fc1c93d36747b75af, 92c736866244340497a8a65afe2ac25354c2bf5e, a7e941a395711791c7e98d9870c6562c2c9e9ef2 |
| Linux | Linux Kernel | 4.11 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 | 5.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 NVD.
Official description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: fix use-after-free on marvell probe failure Make sure to stop any TX URBs submitted during Marvell OOB wakeup configuration on later probe failures to avoid use-after-free in the completion callback. This issue was reported by Sashiko while reviewing a fix for a wakeup source leak in the btusb probe errors paths.
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.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- git.kernel.org/stable/c/0ccb1cb0a464dab78284c34196cd3e8e18bab4c4
- git.kernel.org/stable/c/1edd524de5cc8143ece9c42c466346983dc5b5ed
- git.kernel.org/stable/c/631de465aba7f8ae46478bf5f598111412e8eff8
- git.kernel.org/stable/c/6e1b10df890f4663cb38af9fc1c93d36747b75af
- git.kernel.org/stable/c/838c917a2f16eefe68def800ebf48a2af591149a
- git.kernel.org/stable/c/92c736866244340497a8a65afe2ac25354c2bf5e
- git.kernel.org/stable/c/a7e941a395711791c7e98d9870c6562c2c9e9ef2
- git.kernel.org/stable/c/c5b600a3c05b1a7a110d558df935a8fc8a471c79
Recent Use After Free vulnerabilities
- 9.8 Critical severity
- 7.8 High severity
- 8.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.