LiveActive security incident?Get immediate response
CVE Record

CVE-2024-36893: usb: typec: tcpm: Check for port partner validity before consuming it

In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpm: Check for port partner validity before consuming it typec_register_partner() does not guarantee partner registration to always succeed. In the event of failure, port->partner is set to the error value or NULL. Given that port->partner validity is not checked, this results in the following crash: Unable to handle kernel NULL pointer dereference at virtual address xx pc : run_state_machine+0x1bc8/0x1c08 lr : run_state_machine+0x1b90/0x1c08 .. Call trace: run_state_machine+0x1bc8/0x1c08 tcpm_state_machine_work+0x94/0xe4 kthread_worker_fn+0x118/0x328 kthread+0x1d0/0x23c ret_from_fork+0x10/0x20 To prevent the crash, check for port->partner validity before derefencing it in all the call sites.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel crash bug in USB Type-C power management. If partner registration fails, kernel code may still use an invalid or missing partner pointer, causing a NULL pointer dereference and system crash. The source bundle does not show remote code execution, privilege escalation, or confirmed exploitation.

Executive priority

Treat as a normal availability-focused kernel patching item unless affected systems support critical services or exposed physical USB-C interaction. No source evidence supports emergency response for active exploitation.

Technical view

The flaw is in the Linux kernel USB Type-C TCPM state machine. typec_register_partner() can fail and leave port->partner as NULL or an error value. Subsequent call sites dereference it without validation, producing a kernel NULL pointer dereference. The fix checks port->partner validity before use.

Likely exposure

Linux systems using affected kernel builds with USB Type-C TCPM support are the relevant exposure. Systems without that code path or without affected kernel versions are less likely exposed. Exact exposure depends on distribution backports and hardware configuration.

Exploitation context

CISA KEV status is false in the provided bundle, and no cited source reports active exploitation. The documented impact is a kernel crash, so business risk is primarily availability disruption on affected Linux hosts or devices.

Researcher notes

The evidence supports a missing validity check after typec_register_partner() failure. The public bundle does not provide CVSS, CWE, exploitability details, or distribution-specific fixed package versions, so validation should rely on kernel commit inclusion and vendor backport tracking.

Mitigation direction

  • Apply Linux kernel updates that include the referenced stable fixes.
  • Use distribution vendor advisories to confirm the fixed package version.
  • Prioritize laptops, embedded devices, and servers with USB-C Type-C TCPM hardware.
  • If patching is delayed, review vendor guidance for temporary operational workarounds.

Validation and detection

  • Inventory Linux kernel versions across affected fleets.
  • Identify systems using USB Type-C TCPM-capable hardware or kernel configuration.
  • Confirm installed kernels include vendor backports for CVE-2024-36893.
  • Review system logs for related TCPM state machine kernel crashes.
Prepared
Confidence
high
Sources
7

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-2024-36893 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
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux31220bd89c22a18478f52fcd8069e8e2adb8f4f2, 9b7cd3fe01f0d03cf5820b351a6be2a6e0a6da6f, c97cd0b4b54eb42aed7f6c3c295a2d137f6d2416, c97cd0b4b54eb42aed7f6c3c295a2d137f6d2416, c97cd0b4b54eb42aed7f6c3c295a2d137f6d2416, 2897b36d2482b84f35e659989d5cb4501fb31ccd, cbcf107780aecf51aba68488044a416d95060b6dunaffected
LinuxLinux6.6, 0, 5.15.168, 6.1.91, 6.6.31, 6.8.10, 6.9affected
Weakness

CWE details

No CWE listed

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