CyberSecBulletin
CVE-2026-64020NVD status: Modified

Linux: Missing Release of Memory after Effective Lifetime

CVE-2026-64020 is a high-severity missing release of memory after effective lifetime vulnerability in Linux, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions b9390aa62fdcabdaac2d09545be05901f6cecaf5, 24ea0de233d9ebb5ebd6f6018eaf2084af25e3dd, 85686c72966c5ee637893f124ddb31a1cace7bee 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.61% 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 b9390aa62fdcabdaac2d09545be05901f6cecaf5 or 24ea0de233d9ebb5ebd6f6018eaf2084af25e3dd or 85686c72966c5ee637893f124ddb31a1cace7bee, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 7.0.11 or a later version.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxb8b7570a7ec872f2a27b775c4f8710ca8a357adf up to, but not including, b9390aa62fdcabdaac2d09545be05901f6cecaf5; b8b7570a7ec872f2a27b775c4f8710ca8a357adf up to, but not including, 24ea0de233d9ebb5ebd6f6018eaf2084af25e3dd; b8b7570a7ec872f2a27b775c4f8710ca8a357adf up to, but not including, 85686c72966c5ee637893f124ddb31a1cace7bee; 6.17b9390aa62fdcabdaac2d09545be05901f6cecaf5, 24ea0de233d9ebb5ebd6f6018eaf2084af25e3dd, 85686c72966c5ee637893f124ddb31a1cace7bee
LinuxLinux Kernel6.17 up to, but not including, 7.0.11; 7.17.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
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

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

Official description

In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix dma_vecs leak on p2p memory We don't unmap P2P memory, so we don't need to track it. The dma_vec allocation was getting leaked on the completion.

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

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

References

Recent Missing Release of Memory after Effective Lifetime vulnerabilities

Spotted an error? Tell us.