dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53037

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 5.10.258 / 5.15.209 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A deadlock vulnerability exists in the Linux kernel's USB HID driver (hid_post_reset and hid_pre_reset functions). When a USB device contains both HID and storage/UAS components that must be reset together, memory allocations using standard flags can trigger block IO, which deadlocks on a mutex held during device reset in the error handling path. The fix requires using GFP_NOIO for all allocations in these functions to prevent block IO during the reset sequence.

MitigationApply the kernel patch to change memory allocation flags from GFP_KERNEL or similar to GFP_NOIO in hid_pre_reset() and hid_post_reset() functions. This prevents block IO during the device reset error handling path, eliminating the deadlock condition.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 3.5, < 5.10.258>= 5.11, < 5.15.209>= 5.16, < 6.1.175>= 6.2, < 6.6.141>= 6.7, < 6.12.91>= 6.13, < 6.18.33>= 6.19, < 7.0.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify kernel version
    Run 'uname -r' or check /proc/version to get the running kernel version
    Affected if The version falls within any of the affected ranges: >= 3.5, < 5.10.258; >= 5.11, < 5.15.209; >= 5.16, < 6.1.175; >= 6.2, < 6.6.141; >= 6.7, < 6.12.91; >= 6.13, < 6.18.33; >= 6.19, < 7.0.10
  2. Check for USB HID devices in use
    Run 'lsusb' or check /sys/bus/usb/devices/ to enumerate connected USB devices
    Affected if Any USB Human Interface Devices such as keyboards, mice, or tablets are connected
  3. Identify composite USB devices with storage or UAS
    For each USB device, check if it exposes both HID and mass storage interfaces: run 'lsusb -v' and look for devices with both Interface Class 03 (HID) and Interface Class 08 (Mass Storage) or Interface Class 97 (UAS)
    Affected if Any connected USB device exposes both HID and storage/UAS interfaces in a single composite device (this triggers the reset sequence that can deadlock)
  4. Verify the vulnerable code path exists
    Check the kernel source for drivers/hid/usbhid/hid-core.c - examine the hid_pre_reset and hid_post_reset functions for memory allocations using GFP_KERNEL or similar blocking flags (rather than GFP_NOIO)
    Affected if The functions contain allocations with GFP_KERNEL or GFP_ATOMIC rather than GFP_NOIO, indicating the vulnerable code is present

You are affected if your kernel version is within the affected ranges AND you have composite USB devices that combine HID and storage/UAS functionality, triggering the reset sequence that can deadlock on memory allocations that block on I/O.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.10.258 / 5.15.209 / 6.1.175 or later
Fixed in 5.10.2585.15.2096.1.175
Interim mitigation

Apply the kernel patch to change memory allocation flags from GFP_KERNEL or similar to GFP_NOIO in hid_pre_reset() and hid_post_reset() functions. This prevents block IO during the device reset error handling path, eliminating the deadlock condition.

Recommended fix High confidence

Kernel >= 5.10.258, >= 5.15.209, >= 6.1.175, >= 6.6.141, or 6.7+

  1. Identify current kernel version using `uname -r`
  2. Determine which version branch your current kernel belongs to (e.g., 5.10.x, 5.15.x, 6.1.x, or 6.2.x+)
  3. For 5.10.x branch: upgrade to kernel >= 5.10.258
  4. For 5.11-5.15.x branch: upgrade to kernel >= 5.15.209
  5. For 5.16-6.1.x branch: upgrade to kernel >= 6.1.175
  6. For 6.2-6.6.x branch: upgrade to kernel >= 6.6.141
  7. Alternatively, upgrade to kernel 6.7 or later which contains the fix
  8. Apply the kernel upgrade via distribution package manager (e.g., `apt-get dist-upgrade`, `yum update`, or `dnf upgrade`)
Caveat Kernel upgrades may require rebooting services; ensure application compatibility with newer kernel versions before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53037 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53037 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data