CVE-2026-46134
Awaiting Analysis Awaiting Analysis - Queue
Mutex Not Initialized in Cros EC TypeC Thunderbolt Registration

Publication date: 2026-05-28

Last updated on: 2026-05-28

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: platform/chrome: cros_ec_typec: Init mutex in Thunderbolt registration cros_typec_register_thunderbolt() missed initializing the `adata->lock` mutex. This leads to a NULL dereference when the mutex is later acquired (e.g. in cros_typec_altmode_work()). Initialize the mutex in cros_typec_register_thunderbolt() to fix the issue.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-28
Last Modified
2026-05-28
Generated
2026-05-28
AI Q&A
2026-05-28
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in the Linux kernel's platform/chrome component related to Thunderbolt registration. Specifically, the function cros_typec_register_thunderbolt() failed to initialize a mutex called adata->lock. Because this mutex was not initialized, attempts to acquire it later (such as in the cros_typec_altmode_work() function) could lead to a NULL pointer dereference, causing a potential crash or instability. The issue was fixed by properly initializing the mutex in the registration function.


How can this vulnerability impact me? :

The impact of this vulnerability is that it can cause a NULL pointer dereference in the Linux kernel when handling Thunderbolt registration. This can lead to system crashes or instability, potentially causing denial of service or unexpected behavior on affected systems using this kernel component.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart