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-2025-38404usb: typec: displayport: Fix potential deadlock

Description

In the Linux kernel, the following vulnerability has been resolved: usb: typec: displayport: Fix potential deadlock The deadlock can occur due to a recursive lock acquisition of `cros_typec_altmode_data::mutex`. The call chain is as follows: 1. cros_typec_altmode_work() acquires the mutex 2. typec_altmode_vdm() -> dp_altmode_vdm() -> 3. typec_altmode_exit() -> cros_typec_altmode_exit() 4. cros_typec_altmode_exit() attempts to acquire the mutex again To prevent this, defer the `typec_altmode_exit()` call by scheduling it rather than calling it directly from within the mutex-protected context.

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 10 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-2025-38404, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.16% · top 95% 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected e0359c66c1beccbe90119a63391678eabda38007 – < 749d9076735fb497aae60fbea9fff563f9ea3254
    • affected e3fb6c2c3939b4aad203cacdd613a62ce1fd032c – < eb08fca56f1f39e4038cb9bac9864464b13b00aa
    • affected 56846793f105cf2b39ecbde4f3ae86342091f6fc – < 7be0d1ea71f52595499da39cea484a895e8ed042
    • affected 8e8a69b1f8c59f0505f8a1c0fb77191f27b75011 – < 76cf1f33e7319fe74c94ac92f9814094ee8cc84b
    • affected 8851e40587013db00b71d4aeaae30f5fd59b0eec – < 63cff9f57e86b2dc25d7487ca0118df89a665296
    • affected 10cc2cfd3e5d0e0ec7590c4bee8bcea10e5492c4 – < c782f98eef14197affa8a7b91e6981420f109ea9
    • affected 8f6a4fa7b663468bb304cb885b93326e025ae005 – < 80c25d7916a44715338d4f8924c8e52af50d0b9f
    • affected b4b38ffb38c91afd4dc387608db26f6fc34ed40b – < 099cf1fbb8afc3771f408109f62bdec66f85160e
  • Linux · Linux

    • affected 6.1.143 – < 6.1.144
    • affected 6.6.96 – < 6.6.97
    • affected 6.12.36 – < 6.12.37
    • affected 6.15.5 – < 6.15.6

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .