Linux: Use After Free
CVE-2026-64001 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 d9df965284abde27ba6bfbdfc8407697cf6802f1, 8be4efd0dc0093eb7a02ad1aac936bca2a1f04ce, e13922bb97b4e6f94f8ac02d034f2d4bd65eeb3c 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.13% 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 d9df965284abde27ba6bfbdfc8407697cf6802f1 or 8be4efd0dc0093eb7a02ad1aac936bca2a1f04ce or e13922bb97b4e6f94f8ac02d034f2d4bd65eeb3c or be387230dc22d870afd0e5d35912b07c2bc323bd, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.12.93 or 6.18.35 or 7.0.12, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 060d77b9c04acd7aef60790398a53f731db8c8fe up to, but not including, d9df965284abde27ba6bfbdfc8407697cf6802f1; 060d77b9c04acd7aef60790398a53f731db8c8fe up to, but not including, 8be4efd0dc0093eb7a02ad1aac936bca2a1f04ce; 060d77b9c04acd7aef60790398a53f731db8c8fe up to, but not including, e13922bb97b4e6f94f8ac02d034f2d4bd65eeb3c; 060d77b9c04acd7aef60790398a53f731db8c8fe up to, but not including, be387230dc22d870afd0e5d35912b07c2bc323bd; 060d77b9c04acd7aef60790398a53f731db8c8fe up to, but not including, 4cc54bdd54b337e77115be5b55577d1c58608eae; 2.6.17 | d9df965284abde27ba6bfbdfc8407697cf6802f1, 8be4efd0dc0093eb7a02ad1aac936bca2a1f04ce, e13922bb97b4e6f94f8ac02d034f2d4bd65eeb3c, be387230dc22d870afd0e5d35912b07c2bc323bd, 4cc54bdd54b337e77115be5b55577d1c58608eae |
| Linux | Linux Kernel | 2.6.17 up to, but not including, 6.12.93; 6.13 up to, but not including, 6.18.35; 6.19 up to, but not including, 7.0.12; 7.1 | 6.12.93, 6.18.35, 7.0.12 |
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: ALSA: pcm: oss: Fix setup list UAF on proc write error snd_pcm_oss_proc_write() links a newly allocated setup entry into the OSS setup list before duplicating the task name. If the task-name allocation fails, the error path frees the already linked entry and leaves setup_list pointing at freed memory. A later OSS device open can then walk the stale list entry in snd_pcm_oss_look_for_setup() and dereference freed memory. Allocate the task name and initialize the setup entry before publishing the entry on setup_list. Also fetch the initial proc read iterator only after taking setup_mutex, so all setup_list traversal follows the same list lifetime rules.
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.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
Recent Use After Free vulnerabilities
- 8.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 7.8 High severity
- 9.8 Critical severity
- 8.8 High severity
Spotted an error? Tell us.