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-2026-93214usb: gadget: f_tcm: fix deadlock in usbg_make_tpg()

Description

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_tcm: fix deadlock in usbg_make_tpg() usbg_make_tpg() held dep_lock while calling configfs_depend_item_unlocked(), which acquires the configfs root inode lock when operating across subsystems. This creates a circular lock dependency with configfs_rmdir(): dep_lock -> configfs root inode lock -> su_mutex -> dep_lock In usbg_make_tpg(), dep_lock only serialized the read of opts->ready, which is a monotonic flag that transitions from false to true exactly once (in tcm_set_name()) and never reverts. Remove dep_lock from usbg_make_tpg() entirely and use READ_ONCE/WRITE_ONCE to access opts->ready locklessly instead.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 25 days 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: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (17 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 4bb8548df632187d5db50878e71804af5f7c51ad – < abad5daa41cf5d0a0a9cba0397d3a0e7f11e0277
    • affected 4bb8548df632187d5db50878e71804af5f7c51ad – < 3639438a4c83ffc2e564c8c010b92137c5d11cfa
    • affected 4bb8548df632187d5db50878e71804af5f7c51ad – < 78a14ea2284825055ab6c2a1f3489510f560f3a2
    • affected 4bb8548df632187d5db50878e71804af5f7c51ad – < eef3e62f90d86c1c5651742f84ecc9db1814a893
    • affected 4bb8548df632187d5db50878e71804af5f7c51ad – < f81a2da137b029a282b9bc64d2f267d242948659
    • affected 4bb8548df632187d5db50878e71804af5f7c51ad – < 6bcd9ee6ad6989d1d85a7459687e45b7ad7568d9
    • affected 4bb8548df632187d5db50878e71804af5f7c51ad – < d90b0f90e30cd59b36005a4016b15cf02bcd7fb2
    • affected 4bb8548df632187d5db50878e71804af5f7c51ad – < 9dbf74f4022f80f7669d2b3c22c5deb46c1b5674
  • Linux · Linux

    • affected 4.5
    • unaffected < 4.5
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .