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-2023-54299usb: typec: bus: verify partner exists in typec_altmode_attention

Description

In the Linux kernel, the following vulnerability has been resolved: usb: typec: bus: verify partner exists in typec_altmode_attention Some usb hubs will negotiate DisplayPort Alt mode with the device but will then negotiate a data role swap after entering the alt mode. The data role swap causes the device to unregister all alt modes, however the usb hub will still send Attention messages even after failing to reregister the Alt Mode. type_altmode_attention currently does not verify whether or not a device's altmode partner exists, which results in a NULL pointer error when dereferencing the typec_altmode and typec_altmode_ops belonging to the altmode partner. Verify the presence of a device's altmode partner before sending the Attention message to the Alt Mode driver.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 4 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (15 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 8a37d87d72f0c69f837229c04d2fcd7117ea57e7 – < 5f71716772b88cbe0e1788f6a38d7871aff2120b
    • affected 8a37d87d72f0c69f837229c04d2fcd7117ea57e7 – < 38e1f2ee82bacbbfded8f1c06794a443d038d054
    • affected 8a37d87d72f0c69f837229c04d2fcd7117ea57e7 – < 0ad6bad31da692f8d7acacab07eabe7586239ae0
    • affected 8a37d87d72f0c69f837229c04d2fcd7117ea57e7 – < 0d3b5fe47938e9c451466845304a2bd74e967a80
    • affected 8a37d87d72f0c69f837229c04d2fcd7117ea57e7 – < d49547950bf7f3480d6ca05fe055978e5f0d9e5b
    • affected 8a37d87d72f0c69f837229c04d2fcd7117ea57e7 – < 1101867a1711c27d8bbe0e83136bec47f8c1ca2a
    • affected 8a37d87d72f0c69f837229c04d2fcd7117ea57e7 – < f23643306430f86e2f413ee2b986e0773e79da31
  • Linux · Linux

    • affected 4.19
    • unaffected < 4.19
    • unaffected 5.4.257 – ≤ 5.4.*
    • unaffected 5.10.195 – ≤ 5.10.*
    • unaffected 5.15.132 – ≤ 5.15.*
    • unaffected 6.1.53 – ≤ 6.1.*
    • unaffected 6.4.16 – ≤ 6.4.*
    • unaffected 6.5.3 – ≤ 6.5.*
    • unaffected 6.6 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .