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-64343USB: ldusb: fix use-after-free on disconnect race

Description

In the Linux kernel, the following vulnerability has been resolved: USB: ldusb: fix use-after-free on disconnect race mutex_unlock() may access the mutex structure after releasing the lock and therefore cannot be used to manage lifetime of objects directly (unlike spinlocks and refcounts). [1][2] Use a kref to release the driver data to avoid use-after-free in mutex_unlock() when release() races with disconnect(). [1] a51749ab34d9 ("locking/mutex: Document that mutex_unlock() is non-atomic") [2] 2b9d9e0a9ba0 ("locking/mutex: Clarify that mutex_unlock(), and most other sleeping locks, can still use the lock object after it's unlocked")

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 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-2026-64343, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (16 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: High 7.8.

Affected products

  • Linux · Linux

    • affected ce0d7d3f575fc1ba6a89c3c651e710355590daff – < fc55923a972e715f9a27187b47d4920709e23d85
    • affected ce0d7d3f575fc1ba6a89c3c651e710355590daff – < e5a9bdce4bfd3e2226b5f3df5fb8385d6935ee69
    • affected ce0d7d3f575fc1ba6a89c3c651e710355590daff – < af59829e67e11ba2511a9f8e4b9111afc7d1f550
    • affected ce0d7d3f575fc1ba6a89c3c651e710355590daff – < 02ca08fff74cf9b0a3c4d2cacde1c6edeeb95bb4
    • affected ce0d7d3f575fc1ba6a89c3c651e710355590daff – < d8f69404e1d671326f86d378b9f5bfbd56490e9d
    • affected ce0d7d3f575fc1ba6a89c3c651e710355590daff – < 2107a4fc8ff1cf1d52f416c1e5cc8e97413a5915
    • affected ce0d7d3f575fc1ba6a89c3c651e710355590daff – < a3e794136ab5e3ad1e7019175a4b837aec86db4b
    • affected ce0d7d3f575fc1ba6a89c3c651e710355590daff – < 19bdfc7b3c179331eafa423d87e1336f43bbfeb8
  • Linux · Linux

    • affected 2.6.26
    • unaffected < 2.6.26
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .