Linux Kernel up to 6.5.2 typec_altmode_attention null pointer dereference

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 6.5.2. It has been rated as critical. Impacted is the function typec_altmode_attention. The manipulation leads to null pointer dereference.
This vulnerability is traded as CVE-2023-54299. There is no exploit available.
Upgrading the affected component is advised.
Details
A vulnerability was found in Linux Kernel up to 6.5.2. It has been rated as critical. This issue affects the function typec_altmode_attention. The manipulation with an unknown input leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. Impacted is availability. The summary by CVE is:
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.
The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2023-54299 since 12/30/2025. Technical details are known, but no exploit is available.
Upgrading to version 5.4.257, 5.10.195, 5.15.132, 6.1.53, 6.4.16 or 6.5.3 eliminates this vulnerability. Applying the patch 5f71716772b88cbe0e1788f6a38d7871aff2120b/38e1f2ee82bacbbfded8f1c06794a443d038d054/0ad6bad31da692f8d7acacab07eabe7586239ae0/0d3b5fe47938e9c451466845304a2bd74e967a80/d49547950bf7f3480d6ca05fe055978e5f0d9e5b/1101867a1711c27d8bbe0e83136bec47f8c1ca2a/f23643306430f86e2f413ee2b986e0773e79da31 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-2941). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- Open Source Linux Kernel
Product
Type
Vendor
Name
Version
- 5.4.256
- 5.10.194
- 5.15.131
- 6.1.0
- 6.1.1
- 6.1.2
- 6.1.3
- 6.1.4
- 6.1.5
- 6.1.6
- 6.1.7
- 6.1.8
- 6.1.9
- 6.1.10
- 6.1.11
- 6.1.12
- 6.1.13
- 6.1.14
- 6.1.15
- 6.1.16
- 6.1.17
- 6.1.18
- 6.1.19
- 6.1.20
- 6.1.21
- 6.1.22
- 6.1.23
- 6.1.24
- 6.1.25
- 6.1.26
- 6.1.27
- 6.1.28
- 6.1.29
- 6.1.30
- 6.1.31
- 6.1.32
- 6.1.33
- 6.1.34
- 6.1.35
- 6.1.36
- 6.1.37
- 6.1.38
- 6.1.39
- 6.1.40
- 6.1.41
- 6.1.42
- 6.1.43
- 6.1.44
- 6.1.45
- 6.1.46
- 6.1.47
- 6.1.48
- 6.1.49
- 6.1.50
- 6.1.51
- 6.1.52
- 6.4.0
- 6.4.1
- 6.4.2
- 6.4.3
- 6.4.4
- 6.4.5
- 6.4.6
- 6.4.7
- 6.4.8
- 6.4.9
- 6.4.10
- 6.4.11
- 6.4.12
- 6.4.13
- 6.4.14
- 6.4.15
- 6.5.0
- 6.5.1
- 6.5.2
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.4.257/5.10.195/5.15.132/6.1.53/6.4.16/6.5.3
Patch: 5f71716772b88cbe0e1788f6a38d7871aff2120b/38e1f2ee82bacbbfded8f1c06794a443d038d054/0ad6bad31da692f8d7acacab07eabe7586239ae0/0d3b5fe47938e9c451466845304a2bd74e967a80/d49547950bf7f3480d6ca05fe055978e5f0d9e5b/1101867a1711c27d8bbe0e83136bec47f8c1ca2a/f23643306430f86e2f413ee2b986e0773e79da31
Timeline
12/30/2025 Advisory disclosed12/30/2025 CVE reserved
12/30/2025 VulDB entry created
01/01/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2023-54299 (🔒)
GCVE (CVE): GCVE-0-2023-54299
GCVE (VulDB): GCVE-100-338849
CERT Bund: WID-SEC-2025-2941 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service
Entry
Created: 12/30/2025 15:57Updated: 01/01/2026 21:06
Changes: 12/30/2025 15:57 (59), 01/01/2026 21:06 (7)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.