LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46134: platform/chrome: cros_ec_typec: Init mutex in Thunderbolt registration

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash affected systems when ChromeOS EC Type-C Thunderbolt handling reaches an uninitialized mutex. The public record describes a NULL dereference, which points mainly to stability and availability risk. No CVSS score, CWE, or active exploitation evidence is provided.

Executive priority

Track and remediate through normal kernel patch management, with higher priority for fleets using affected Type-C or Thunderbolt hardware. Current sources do not justify emergency treatment, but kernel crashes can create operational disruption.

Technical view

The cros_ec_typec Thunderbolt registration path failed to initialize adata->lock in cros_typec_register_thunderbolt(). Later acquisition, such as from cros_typec_altmode_work(), can dereference NULL. The kernel fix initializes the mutex during Thunderbolt registration.

Likely exposure

Exposure appears limited to Linux systems using the platform/chrome cros_ec_typec Type-C/Thunderbolt path on affected kernel versions or downstream builds. Exact distribution package impact is not established in the supplied sources and should be mapped through vendor advisories.

Exploitation context

The supplied sources do not report exploitation in the wild, and KEV status is false. They also do not define an attack vector, required privileges, or remote reachability. Treat this as a kernel availability issue until vendor analysis says otherwise.

Researcher notes

Evidence is narrow but clear: the bug is an uninitialized mutex in Thunderbolt registration, fixed by mutex initialization. Missing data includes CVSS, CWE, exploitability details, and downstream distro status. Validate against the exact kernel tree or vendor backport.

Mitigation direction

  • Update to a kernel build containing the referenced stable fixes.
  • Check Linux distribution advisories for affected package versions and backports.
  • Prioritize systems with ChromeOS EC Type-C or Thunderbolt functionality.
  • Avoid relying on upstream version strings alone; confirm downstream patch status.

Validation and detection

  • Inventory Linux kernel versions across potentially affected devices.
  • Confirm whether cros_ec_typec and Thunderbolt paths are present or enabled.
  • Verify the kernel source or package changelog includes the stable fix commit.
  • Review kernel logs for NULL dereference or oops events involving cros_typec_altmode_work().
Prepared
Confidence
medium
Sources
5

Public sources used

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-2026-46134 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3b00be26b16ad72c85624ada08cbae2d2c57b6e9, 3b00be26b16ad72c85624ada08cbae2d2c57b6e9, 3b00be26b16ad72c85624ada08cbae2d2c57b6e9unaffected
LinuxLinux6.14, 0, 6.18.30, 7.0.7, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.