CVE-2026-53037
CVE-2026-53037 is a security vulnerability that is still awaiting full analysis and scoring. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.
Key facts
- EPSS exploit prediction: 0% (7th percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2026-38905
- Published:
- Last modified:
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.
Frequently asked questions
- What is CVE-2026-53037?
- 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.
- Is CVE-2026-53037 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (7th percentile), an estimate of the probability of exploitation in the next 30 days.
- How do I fix CVE-2026-53037?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- Does CVE-2026-53037 have an EU (EUVD) identifier?
- Yes. CVE-2026-53037 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-38905.
- When was CVE-2026-53037 published?
- CVE-2026-53037 was published on 2026-06-24.
References
- https://git.kernel.org/stable/c/4e900465296ce9fb12ed47dc77389b8dde95bfe0
- https://git.kernel.org/stable/c/56d318ef8766f0deb08517fd8f3007256ea7997d
- https://git.kernel.org/stable/c/8df2c1b47ee3cd50fd454f75c7a7e2ae8a6adf72
- https://git.kernel.org/stable/c/90550af0aad5e75110073c501e4fb42fca20ff80
- https://git.kernel.org/stable/c/ad4505d2ab3aaac6498f17649608e70e80034bf2
- https://git.kernel.org/stable/c/b3d16611d7cd78e9d5c6baa19b61b7caf9f1ab5e
- https://git.kernel.org/stable/c/c7abd0e6c87441e99c759d40eb6fe589634e3041
- https://git.kernel.org/stable/c/eeceb6f4dd42065fdda3a526a93d08b8fb90fb69