BaseFortify

Publication date: 2025-12-30

Last updated on: 2025-12-31

Assigner: kernel.org

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2025-12-30

Last Modified

2025-12-31

Generated

2026-07-07

AI Q&A

2025-12-30

EPSS Evaluated

2026-07-05

NVD

CVE-2023-54299

EUVD

EUVD-2023-60505

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability occurs in the Linux kernel's USB Type-C subsystem. Some USB hubs negotiate DisplayPort Alternate Mode with a device, then perform a data role swap after entering the alternate mode. This swap causes the device to unregister all alternate modes, but the USB hub continues to send Attention messages. The function handling these messages does not verify if the device's alternate mode partner exists, leading to a NULL pointer dereference error when accessing the partner's data structures.

Impact Analysis

The vulnerability can cause a NULL pointer dereference in the Linux kernel, which may lead to a kernel crash or system instability when a USB hub sends Attention messages after a data role swap. This can result in denial of service or unexpected behavior on affected systems.

Hi! I’m here to help you understand CVE-2023-54299. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70