Linux: Missing Release of Memory after Effective Lifetime
CVE-2026-64485 is a high-severity missing release of memory after effective lifetime 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 b27a75d42044d9d4709095617730b91b1c4af423, 426a9947a38d272d0e19c031658da68e31128667, 4a60127debb9e370d6c0e22a307326b624a141f3 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.17% 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 b27a75d42044d9d4709095617730b91b1c4af423 or 426a9947a38d272d0e19c031658da68e31128667 or 4a60127debb9e370d6c0e22a307326b624a141f3, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.18.39 or 7.1.4, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 04177158cf98a79744937893b100020d77e6f9ac up to, but not including, b27a75d42044d9d4709095617730b91b1c4af423; 04177158cf98a79744937893b100020d77e6f9ac up to, but not including, 426a9947a38d272d0e19c031658da68e31128667; 04177158cf98a79744937893b100020d77e6f9ac up to, but not including, 4a60127debb9e370d6c0e22a307326b624a141f3; 6.13 | b27a75d42044d9d4709095617730b91b1c4af423, 426a9947a38d272d0e19c031658da68e31128667, 4a60127debb9e370d6c0e22a307326b624a141f3 |
| Linux | Linux Kernel | 6.13 up to, but not including, 6.18.39; 6.19 up to, but not including, 7.1.4 | 6.18.39, 7.1.4 |
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: ALSA: compress: Fix task creation error unwind snd_compr_task_new() allocates the driver task before validating the returned DMA buffers and reserving file descriptors. When either of those later steps fails, the core frees its task wrapper and DMA-buffer references without calling the driver's task_free() callback. Any driver resources allocated by task_create() are therefore leaked. The dual-fd allocation path also jumps to cleanup without storing the negative get_unused_fd_flags() result in retval. Since retval still contains the successful task_create() return value, TASK_CREATE can incorrectly report success although the task was discarded. Preserve the fd allocation errors and call task_free() when failure occurs after a successful task_create() callback.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Release of Memory after Effective Lifetime
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
How developers prevent this class of flaw
- Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone. For example, glibc in Linux provides protection against free of invalid pointers. When using Xcode to target OS X or iOS, enable automatic reference counting (ARC). To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std
- Use an abstraction library to abstract away risky APIs. Not a complete solution.
- Consider using the Boehm-Demers-Weiser garbage collector (bdwgc), which can help avoid leaks.
More Missing Release of Memory after Effective Lifetime vulnerabilities (CWE-401)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Recent Missing Release of Memory after Effective Lifetime vulnerabilities
- 7.0 High severity
- 7.8 High severity
- 7.5 High severity
- 8.7 High severity
- 9.4 Critical severity
- 7.5 High severity
Spotted an error? Tell us.