Quick answers
- Is CVE-2026-97483 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-97483 being exploited in the wild.
- How severe is CVE-2026-97483?
- Informational severity, published 24 September 2026.
- Which products and versions are affected?
- Linux kernel 2.6.11 through 7.2 and later.
- Is there a fix for CVE-2026-97483?
- A patch was published on 2026-05-22: Fix merged upstream Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-97483 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-97483?
- Check whether you run Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A deadlock condition occurs in the USB Host Controller Driver (HCD) when rh_call_control() performs memory allocation with GFP_KERNEL flags during root hub control transfers initiated from the SCSI error handler. The vulnerability stems from improper handling of memory allocation flags when resetting devices—the mem_flags parameter passed to usb_submit_urb() was not propagated to internal memory allocation calls. The fix modifies rh_call_control() and rh_urb_enqueue() to accept and use the mem_flags parameter, replacing hardcoded GFP_KERNEL with the appropriate flags.
Affected products
- Linux Kernel 2.6.11 through 7.2 and later
Timeline
- 2026-09-24: disclosed
- 2026-05-22: patched: Fix merged upstream