Kernel crash via unchecked Alt Mode partner
Published Dec 30, 2025 · Updated Dec 30, 2025
NULL pointer dereference in affected Linux kernels allows physically proximate attackers to crash the kernel through a USB Type-C hub. The typec_altmode_attention() path sends an Attention event without confirming that a data-role swap left an Alt Mode partner, then dereferences the missing partner's typec_altmode and operations pointers. Triggering requires USB-C DisplayPort Alt Mode and a hub that swaps roles, unregisters alternate modes, and keeps sending Attention messages; systems lacking that capability are unaffected.
Summary
What happened
NULL pointer dereference in affected Linux kernels allows physically proximate attackers to crash the kernel through a USB Type-C hub. The typec_altmode_attention() path sends an Attention event without confirming that a data-role swap left an Alt Mode partner, then dereferences the missing partner's typec_altmode and operations pointers. Triggering requires USB-C DisplayPort Alt Mode and a hub that swaps roles, unregisters alternate modes, and keeps sending Attention messages; systems lacking that capability are unaffected.
The record
- CVE
- CVE-2023-54299
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 2025Record 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=4.19
- Affected versionversion=8a37d87d72f0c69f837229c04d2fcd7117ea57e7 <0ad6bad31da692f8d7acacab07eabe7586239ae0
- Affected versionversion=8a37d87d72f0c69f837229c04d2fcd7117ea57e7 <0d3b5fe47938e9c451466845304a2bd74e967a80
- Affected versionversion=8a37d87d72f0c69f837229c04d2fcd7117ea57e7 <1101867a1711c27d8bbe0e83136bec47f8c1ca2a
- Affected versionversion=8a37d87d72f0c69f837229c04d2fcd7117ea57e7 <38e1f2ee82bacbbfded8f1c06794a443d038d054
- Affected versionversion=8a37d87d72f0c69f837229c04d2fcd7117ea57e7 <5f71716772b88cbe0e1788f6a38d7871aff2120b
- Affected versionversion=8a37d87d72f0c69f837229c04d2fcd7117ea57e7 <d49547950bf7f3480d6ca05fe055978e5f0d9e5b
- Affected versionversion=8a37d87d72f0c69f837229c04d2fcd7117ea57e7 <f23643306430f86e2f413ee2b986e0773e79da31
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.
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