Kernel memory corruption via duplicate PD capability free
Published May 1, 2024 · Updated May 11, 2026
Double free in the Linux kernel USB Type-C TCPM subsystem in 6.8 allows local users to corrupt kernel memory during port registration. The teardown path frees the same PD capability through pd_capabilities_release() and then again explicitly in tcpm_port_unregister_pd(). The gate is local low-privileged access plus a TCPM-capable Type-C port path; the observed failure is kernel-memory corruption detected by KASAN.
Summary
What happened
Double free in the Linux kernel USB Type-C TCPM subsystem in 6.8 allows local users to corrupt kernel memory during port registration. The teardown path frees the same PD capability through pd_capabilities_release() and then again explicitly in tcpm_port_unregister_pd(). The gate is local low-privileged access plus a TCPM-capable Type-C port path; the observed failure is kernel-memory corruption detected by KASAN.
The record
- CVE
- CVE-2024-26932
- Published
- May 1, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-415
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=6.8
- Affected versionversion=cd099cde4ed264403b434d8344994f97ac2a4349 <242e425ed580b2f4dbcb86c8fc03a410a4084a69
- Affected versionversion=cd099cde4ed264403b434d8344994f97ac2a4349 <b63f90487bdf93a4223ce7853d14717e9d452856
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
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