Kernel memory corruption via incomplete probe cleanup
Published Jul 25, 2026 · Updated Jul 25, 2026
Incomplete cleanup in the RT1711H USB Type-C driver in affected Linux Kernel releases allows local users to corrupt kernel memory. After tcpci_register_port() succeeds, rt1711h_probe() returns on interrupt-request or alert-enable failure without unregistering the TCPCI port, leaving queued work and a timer to reference freed memory. A basic local user must induce a later probe failure and can then cause information disclosure, arbitrary kernel-memory writes, or an oops, panic, or persistent hang.
Summary
What happened
Incomplete cleanup in the RT1711H USB Type-C driver in affected Linux Kernel releases allows local users to corrupt kernel memory. After tcpci_register_port() succeeds, rt1711h_probe() returns on interrupt-request or alert-enable failure without unregistering the TCPCI port, leaving queued work and a timer to reference freed memory. A basic local user must induce a later probe failure and can then cause information disclosure, arbitrary kernel-memory writes, or an oops, panic, or persistent hang.
The record
- CVE
- CVE-2026-64463
- Published
- Jul 25, 2026
- Updated
- Jul 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-459, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 25, 2026CVE publishedPublication date reported by the CVE source.
- Jul 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=302c570bf36e997d55ad0d60628a2feec76954a4 <569f18a83eed0b0be4615f0c7bed40fb5c50e2e6
- Affected versionversion=302c570bf36e997d55ad0d60628a2feec76954a4 <94b1abf1af94aa5a355e9f03675e07bccfc41c4b
- Affected versionversion=302c570bf36e997d55ad0d60628a2feec76954a4 <ce2e36e8759dfbfe546723810c306f42f484866d
- Affected versionversion=302c570bf36e997d55ad0d60628a2feec76954a4 <e5406c8fb71cd2f89a46300a746f6e7972e621e8
- Affected versionversion=302c570bf36e997d55ad0d60628a2feec76954a4 <e8da46d99d3710106e7c44db14566bf9b57386b5
- Affected versionversion=4.19.131 <4.20
- Affected versionversion=4309ab96ab744703871e35d829177dd9347bf643
- Affected versionversion=5.4.50 <5.5
- Affected versionversion=5.7.7 <5.8
- Affected versionversion=5.8
- Affected versionversion=745dcedb896a740825160228f98dbb5725a49f85
- Affected versionversion=895ec8c86e13f85b119c71d5f95491b48867955e
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo