Linux: Missing Release of Memory after Effective Lifetime
CVE-2026-64104 is a high-severity missing release of memory after effective lifetime vulnerability in Linux, with a CVSS 3.1 base score of 8.7 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 bee400ad4f4259c9c0758e4f1960a1eed6f6f9f0, 3d0cd0065deeb054b4b29236432e851806b7cc81, fd948c3f96b18ff9ba7d3e8eae13d196593e1aaf 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 bee400ad4f4259c9c0758e4f1960a1eed6f6f9f0 or 3d0cd0065deeb054b4b29236432e851806b7cc81 or fd948c3f96b18ff9ba7d3e8eae13d196593e1aaf or 6.14, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.14 or 6.18.34 or 7.0.11, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 3e385c0d6ce88ac9916dcf84267bd5855d830748 up to, but not including, bee400ad4f4259c9c0758e4f1960a1eed6f6f9f0; 3e385c0d6ce88ac9916dcf84267bd5855d830748 up to, but not including, 3d0cd0065deeb054b4b29236432e851806b7cc81; 3e385c0d6ce88ac9916dcf84267bd5855d830748 up to, but not including, fd948c3f96b18ff9ba7d3e8eae13d196593e1aaf; 0b16521f95c875e79d657cb8d6911c15080dbb80; 6.13.8 up to, but not including, 6.14; 6.14 | bee400ad4f4259c9c0758e4f1960a1eed6f6f9f0, 3d0cd0065deeb054b4b29236432e851806b7cc81, fd948c3f96b18ff9ba7d3e8eae13d196593e1aaf, 6.14 |
| Linux | Linux Kernel | 6.13.8 up to, but not including, 6.14; 6.14.1 up to, but not including, 6.18.34; 6.19 up to, but not including, 7.0.11; 6.14; 7.1 | 6.14, 6.18.34, 7.0.11 |
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
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L. Scored by CNA.
Official description
In the Linux kernel, the following vulnerability has been resolved: virt: sev-guest: Explicitly leak pages in unknown state When set_memory_{encrypted,decrypted}() fail, the user cannot know at which point the function failed, meaning that the pages are left in an unknown state from the point of view of the caller. Since the pages may be left in an unencrypted state, they are not suitable for general use, and cannot be returned safely to the buddy allocator. Avoid the issue by never freeing the pages, and then do the proper accounting by calling snp_leak_pages().
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.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Recent Missing Release of Memory after Effective Lifetime vulnerabilities
- 9.4 Critical severity
- 7.5 High severity
- 7.5 High severity
- 7.1 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.