Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 24 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-36893, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 31220bd89c22a18478f52fcd8069e8e2adb8f4f2 – < 2a07e6f0ad8a6e504a3912cfe8dc859b7d0740a5
    • affected 9b7cd3fe01f0d03cf5820b351a6be2a6e0a6da6f – < d56d2ca03cc22123fd7626967d096d8661324e57
    • affected c97cd0b4b54eb42aed7f6c3c295a2d137f6d2416 – < 789326cafbd1f67f424436b6bc8bdb887a364637
    • affected c97cd0b4b54eb42aed7f6c3c295a2d137f6d2416 – < fc2b655cb6dd2b381f1f284989721002e39b6b77
    • affected c97cd0b4b54eb42aed7f6c3c295a2d137f6d2416 – < ae11f04b452b5205536e1c02d31f8045eba249dd
    • affected 2897b36d2482b84f35e659989d5cb4501fb31ccd
    • affected cbcf107780aecf51aba68488044a416d95060b6d
    • affected 5.15.132 – < 5.15.168
    • affected 6.1.53 – < 6.1.91
    • affected 6.4.16 – < 6.5
    • affected 6.5.3 – < 6.6
  • Linux · Linux

    • affected 6.6
    • unaffected < 6.6
    • unaffected 5.15.168 – ≤ 5.15.*
    • unaffected 6.1.91 – ≤ 6.1.*
    • unaffected 6.6.31 – ≤ 6.6.*
    • unaffected 6.8.10 – ≤ 6.8.*
    • unaffected 6.9 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-36893 badge
[![CVE-2024-36893](https://cveledger.app/badge/CVE-2024-36893.svg)](https://cveledger.app/cve/CVE-2024-36893)

Record last updated .