CyberSecBulletin
CVE-2026-64463NVD status: Analyzed

Linux: Missing Release of Memory after Effective Lifetime

Published Updated By the CyberSecBulletin desk

CVE-2026-64463 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 388f5354158fc038214b73baad43a723385fea1e, ce2e36e8759dfbfe546723810c306f42f484866d, 94b1abf1af94aa5a355e9f03675e07bccfc41c4b 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.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 388f5354158fc038214b73baad43a723385fea1e or ce2e36e8759dfbfe546723810c306f42f484866d or 94b1abf1af94aa5a355e9f03675e07bccfc41c4b or e5406c8fb71cd2f89a46300a746f6e7972e621e8, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 4.20 or 5.5 or 5.8 or 6.1.191, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux302c570bf36e997d55ad0d60628a2feec76954a4 up to, but not including, 388f5354158fc038214b73baad43a723385fea1e; 302c570bf36e997d55ad0d60628a2feec76954a4 up to, but not including, ce2e36e8759dfbfe546723810c306f42f484866d; 302c570bf36e997d55ad0d60628a2feec76954a4 up to, but not including, 94b1abf1af94aa5a355e9f03675e07bccfc41c4b; 302c570bf36e997d55ad0d60628a2feec76954a4 up to, but not including, e5406c8fb71cd2f89a46300a746f6e7972e621e8; 302c570bf36e997d55ad0d60628a2feec76954a4 up to, but not including, 569f18a83eed0b0be4615f0c7bed40fb5c50e2e6; 302c570bf36e997d55ad0d60628a2feec76954a4 up to, but not including, e8da46d99d3710106e7c44db14566bf9b57386b5; 4309ab96ab744703871e35d829177dd9347bf643; 895ec8c86e13f85b119c71d5f95491b48867955e; and 5 more ranges388f5354158fc038214b73baad43a723385fea1e, ce2e36e8759dfbfe546723810c306f42f484866d, 94b1abf1af94aa5a355e9f03675e07bccfc41c4b, e5406c8fb71cd2f89a46300a746f6e7972e621e8, 569f18a83eed0b0be4615f0c7bed40fb5c50e2e6, e8da46d99d3710106e7c44db14566bf9b57386b5
LinuxLinux Kernel4.19.131 up to, but not including, 4.20; 5.4.50 up to, but not including, 5.5; 5.7.7 up to, but not including, 5.8; 5.8.1 up to, but not including, 6.1.191; 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; and 2 more ranges4.20, 5.5, 5.8, 6.1.191, 6.6.145, 6.12.96

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: usb: typec: tcpci_rt1711h: unregister TCPCI port with devres rt1711h_probe() registers the TCPCI port before requesting the interrupt and enabling alert interrupts. If either of those later steps fails, the probe function returns without unregistering the TCPCI port. The explicit unregister currently only happens from the remove callback. Register a devres action immediately after tcpci_register_port() succeeds, so tcpci_unregister_port() runs on later probe failures and on driver detach. Drop the remove callback to avoid unregistering the same port twice. This issue was identified during our ongoing static-analysis research while reviewing kernel code.

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. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. 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.