Mutex Not Initialized in Cros EC TypeC Thunderbolt Registration

Publication date: 2026-05-28

Last updated on: 2026-06-24

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-06-24

Generated

2026-07-08

AI Q&A

2026-05-28

EPSS Evaluated

2026-07-06

NVD

CVE-2026-46134

EUVD

EUVD-2026-32761

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	7.1
linux	linux_kernel	7.1
linux	linux_kernel	From 6.19 (inc) to 7.0.7 (exc)
linux	linux_kernel	From 6.14 (inc) to 6.18.30 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-476	The product dereferences a pointer that it expects to be valid but is NULL.

Attack-Flow Graph

Executive Summary

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.

Impact Analysis

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.

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

0/70