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-53037HID: usbhid: fix deadlock in hid_post_reset()

Description

In the Linux kernel, the following vulnerability has been resolved: HID: usbhid: fix deadlock in hid_post_reset() You can build a USB device that includes a HID component and a storage or UAS component. The components can be reset only together. That means that hid_pre_reset() and hid_post_reset() are in the block IO error handling. Hence no memory allocation used in them may do block IO because the IO can deadlock on the mutex held while resetting a device and calling the interface drivers. Use GFP_NOIO for all allocations in them.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 5 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-53037, 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.10% · top 99% of all CVEs (19 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected dc3c78e43469063c5bf4b744214508f94c4129f9 – < 56d318ef8766f0deb08517fd8f3007256ea7997d
    • affected dc3c78e43469063c5bf4b744214508f94c4129f9 – < 90550af0aad5e75110073c501e4fb42fca20ff80
    • affected dc3c78e43469063c5bf4b744214508f94c4129f9 – < eeceb6f4dd42065fdda3a526a93d08b8fb90fb69
    • affected dc3c78e43469063c5bf4b744214508f94c4129f9 – < ad4505d2ab3aaac6498f17649608e70e80034bf2
    • affected dc3c78e43469063c5bf4b744214508f94c4129f9 – < 4e900465296ce9fb12ed47dc77389b8dde95bfe0
    • affected dc3c78e43469063c5bf4b744214508f94c4129f9 – < c7abd0e6c87441e99c759d40eb6fe589634e3041
    • affected dc3c78e43469063c5bf4b744214508f94c4129f9 – < b3d16611d7cd78e9d5c6baa19b61b7caf9f1ab5e
    • affected dc3c78e43469063c5bf4b744214508f94c4129f9 – < 8df2c1b47ee3cd50fd454f75c7a7e2ae8a6adf72
  • Linux · Linux

    • affected 3.5
    • unaffected < 3.5
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.141 – ≤ 6.6.*
    • unaffected 6.12.91 – ≤ 6.12.*
    • unaffected 6.18.33 – ≤ 6.18.*
    • unaffected 7.0.10 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .