Kernel crash via unchecked Type-C partner pointer
Published May 30, 2024 · Updated May 23, 2026
NULL pointer dereference in the USB Type-C TCPM subsystem in Linux allows local users to crash the kernel during partner setup. If typec_register_partner() fails, the TCPM state machine retains an error pointer or NULL in port->partner and dereferences it at multiple call sites. Reachability requires the affected TCPM code and a failed Type-C partner registration; the demonstrated consequence is a kernel crash, not data access or code execution.
Summary
What happened
NULL pointer dereference in the USB Type-C TCPM subsystem in Linux allows local users to crash the kernel during partner setup. If typec_register_partner() fails, the TCPM state machine retains an error pointer or NULL in port->partner and dereferences it at multiple call sites. Reachability requires the affected TCPM code and a failed Type-C partner registration; the demonstrated consequence is a kernel crash, not data access or code execution.
The record
- CVE
- CVE-2024-36893
- Published
- May 30, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 30, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 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=2897b36d2482b84f35e659989d5cb4501fb31ccd
- Affected versionversion=31220bd89c22a18478f52fcd8069e8e2adb8f4f2 <2a07e6f0ad8a6e504a3912cfe8dc859b7d0740a5
- Affected versionversion=5.15.132 <5.15.168
- Affected versionversion=6.1.53 <6.1.91
- Affected versionversion=6.4.16 <6.5
- Affected versionversion=6.5.3 <6.6
- Affected versionversion=6.6
- Affected versionversion=9b7cd3fe01f0d03cf5820b351a6be2a6e0a6da6f <d56d2ca03cc22123fd7626967d096d8661324e57
- Affected versionversion=c97cd0b4b54eb42aed7f6c3c295a2d137f6d2416 <789326cafbd1f67f424436b6bc8bdb887a364637
- Affected versionversion=c97cd0b4b54eb42aed7f6c3c295a2d137f6d2416 <ae11f04b452b5205536e1c02d31f8045eba249dd
- Affected versionversion=c97cd0b4b54eb42aed7f6c3c295a2d137f6d2416 <fc2b655cb6dd2b381f1f284989721002e39b6b77
- Affected versionversion=cbcf107780aecf51aba68488044a416d95060b6d
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