CVE-2026-53037: Linux kernel · HID: usbhid: fix deadlock in hid_post_reset()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in eeceb6f4dd42065fdda3a526a93d08b8fb90fb69 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 16:49 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in eeceb6f4dd42065fdda3a526a93d08b8fb90fb69, c7abd0e6c87441e99c759d40eb6fe589634e3041, b3d16611d7cd78e9d5c6baa19b61b7caf9f1ab5e +5
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
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.
References
- git.kernel.org/stable/c/56d318ef8766f0deb08517fd8f3007256ea7997d (opens in a new tab)
- git.kernel.org/stable/c/90550af0aad5e75110073c501e4fb42fca20ff80 (opens in a new tab)
- git.kernel.org/stable/c/eeceb6f4dd42065fdda3a526a93d08b8fb90fb69 (opens in a new tab)
- git.kernel.org/stable/c/ad4505d2ab3aaac6498f17649608e70e80034bf2 (opens in a new tab)
- git.kernel.org/stable/c/4e900465296ce9fb12ed47dc77389b8dde95bfe0 (opens in a new tab)
- git.kernel.org/stable/c/c7abd0e6c87441e99c759d40eb6fe589634e3041 (opens in a new tab)
- git.kernel.org/stable/c/b3d16611d7cd78e9d5c6baa19b61b7caf9f1ab5e (opens in a new tab)
- git.kernel.org/stable/c/8df2c1b47ee3cd50fd454f75c7a7e2ae8a6adf72 (opens in a new tab)