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

Description

In the Linux kernel, the following vulnerability has been resolved: USB: idmouse: 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-64344, 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 (18 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 54d2bc068fd21bcb096660938bce7c7265613a24 – < 31e75fed8f90cfea9f8285e7ed135b0e452bf872
    • affected 54d2bc068fd21bcb096660938bce7c7265613a24 – < 8d53b14ad4ccbff6d306b3a39c812303f4a87d41
    • affected 54d2bc068fd21bcb096660938bce7c7265613a24 – < f62622e947f82a3854a8502d09492ffbdeb252b4
    • affected 54d2bc068fd21bcb096660938bce7c7265613a24 – < 60fc5ef4ecea3e3d1fe556cecf53ddd13096ef09
    • affected 54d2bc068fd21bcb096660938bce7c7265613a24 – < d0f61acb51a8c8f3fd41c303ddb7770cd83e7ed4
    • affected 54d2bc068fd21bcb096660938bce7c7265613a24 – < 54c2b7356b4aeea467f9fb13b85e9e036bc428cb
    • affected 54d2bc068fd21bcb096660938bce7c7265613a24 – < e88cff5fbaa629f3cab45c8b46f395d62c2eb515
    • affected 54d2bc068fd21bcb096660938bce7c7265613a24 – < ff002c153f9722caece3983cc23dc4d9d4652cb4
  • Linux · Linux

    • affected 2.6.24
    • unaffected < 2.6.24
    • 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-64344 badge
[![CVE-2026-64344](https://cveledger.app/badge/CVE-2026-64344.svg)](https://cveledger.app/cve/CVE-2026-64344)

Record last updated .