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-97483usb: core: hcd: fix possible deadlock in rh control transfers

Description

In the Linux kernel, the following vulnerability has been resolved: usb: core: hcd: fix possible deadlock in rh control transfers >From within the SCSI error handler memory allocations must not trigger IO. Handling errors in UAS and the storage driver may involve resetting a device. The thread doing the reset itself relies on VM magic. However, that is insufficient, as resetting a device involves resuming it. Resumption as well as resetting involves conrol transfers to the parent of the device to be reset. That may be a root hub. Hence usbcore must heed the flags passed to usb_submit_urb() processing control transfers to root hubs. The problem exist since the storage driver has been merged.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 9 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.17% · 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 e57e780b346a7277fdd3bde765d9d8728b99bfa1 – < 8461eda5af77c44d216cec66455bd5b01ee35c9a
    • affected e57e780b346a7277fdd3bde765d9d8728b99bfa1 – < 8f82fc3d72e5feb7a1efae94b51b431c5bf41c86
    • affected e57e780b346a7277fdd3bde765d9d8728b99bfa1 – < 936b08d87c667031725bcc753007e7c1182548c6
    • affected e57e780b346a7277fdd3bde765d9d8728b99bfa1 – < d0291fb4d91982d9f6a680bf759ff0555d351ecb
    • affected e57e780b346a7277fdd3bde765d9d8728b99bfa1 – < fff917c85d37a294397c5440a795591ca9d6b602
    • affected e57e780b346a7277fdd3bde765d9d8728b99bfa1 – < 549672a3fb6b36ea408238f89ecf9f41d2da6225
    • affected e57e780b346a7277fdd3bde765d9d8728b99bfa1 – < d5559f43d76b398392b26a15cbc16d731969cd1c
  • Linux · Linux

    • affected 3.12
    • unaffected < 3.12
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .