CVE-2023-54299: usb: typec: bus: verify partner exists in typec_altmode_attention
In the Linux kernel, the following vulnerability has been resolved:
usb: typec: bus: verify partner exists in typec_altmode_attention
Some usb hubs will negotiate DisplayPort Alt mode with the device
but will then negotiate a data role swap after entering the alt
mode. The data role swap causes the device to unregister all alt
modes, however the usb hub will still send Attention messages
even after failing to reregister the Alt Mode. type_altmode_attention
currently does not verify whether or not a device's altmode partner
exists, which results in a NULL pointer error when dereferencing
the typec_altmode and typec_altmode_ops belonging to the altmode
partner.
Verify the presence of a device's altmode partner before sending
the Attention message to the Alt Mode driver.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel USB-C handling flaw. Certain USB hubs can trigger a kernel NULL pointer error after DisplayPort Alt Mode negotiation and a data role swap. The business concern is reliability: affected systems using USB-C docks or hubs may crash or become unstable.
Executive priority
Treat as a reliability and availability issue for Linux fleets using USB-C peripherals. Prioritize managed workstations, kiosks, and operational systems where unexpected kernel crashes would disrupt work. No source provided evidence of active exploitation.
Technical view
In typec_altmode_attention, the kernel did not verify that an Alt Mode partner still existed before sending an Attention message to the Alt Mode driver. After a data role swap unregisters alt modes, a hub may still send Attention messages, causing dereference of missing partner structures.
Likely exposure
Likely exposure is Linux systems using affected kernel versions with USB Type-C and DisplayPort Alt Mode, especially endpoints connected to USB-C hubs or docks. The bundle does not identify remote exposure or affected distributions.
Exploitation context
The source describes a device-interaction crash condition, not active exploitation. KEV is false, and no cited source claims weaponized exploitation. Practical triggering appears to require a USB-C hub/device behavior that negotiates Alt Mode, then role swaps.
Researcher notes
The fix adds a partner-existence check before Alt Mode Attention handling. The source bundle provides no CVSS, CWE, distribution advisory, or exploit proof. Affected-version data is incomplete, so branch-specific validation should rely on vendor kernel packages and the linked stable commits.
Mitigation direction
Update to a Linux kernel build containing the referenced stable fixes.
Check your Linux distribution’s advisory for the corrected package version.
Prioritize systems that use USB-C docks, hubs, or DisplayPort Alt Mode.
If patching is delayed, reduce exposure to untrusted USB-C peripherals.
Validation and detection
Inventory Linux kernel versions on systems using USB-C docks or hubs.
Compare installed kernels with distribution advisories and referenced stable commits.
Review kernel logs for USB Type-C Alt Mode NULL pointer errors.
Confirm patched systems no longer run affected kernel builds.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2023-54299 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
8Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 30, 2025, 12:23 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.