Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2026-98767

usb: dwc3: gadget: fix IRQ storm on invalid event buffer count

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.15.224, 6.1.191, 6.6.160, 6.12.113, 5.5, and 4 more
None on Exploit-DB, Metasploit or GitHub

Summary

In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: gadget: fix IRQ storm on invalid event buffer count When dwc3_check_event_buf() reads a GEVNTCOUNT value exceeding the event buffer length, commit 63ccd26cd1f6 ("usb: dwc3: gadget: check that event count does not exceed event buffer length") returns IRQ_NONE without writing back GEVNTCOUNT. Since the DWC3 interrupt is level-triggered, the uncleared IRQ source keeps the line asserted, causing a tight IRQ storm that accumulates 99,900 unhandled interrupts and triggers spurious.c:184 BUG -> kernel panic. The resulting call stack: __report_bad_irq+0xac/0xc8 note_interrupt+0x340/0x468 handle_irq_event+0xac/0xc0 handle_fasteoi_irq+0x120/0x228 gic_handle_irq+0x68/0x108 ... kernel BUG at kernel/irq/spurious.c:184 To reproduce, write a bogus value exceeding the event buffer length directly to the GEVNTCOUNT register: devmem <DWC3_BASE + 0xc40c> 4 0x1004 Write the bogus count back to GEVNTCOUNT to clear the IRQ source, consistent with the stale event clearing pattern in dwc3_event_buffers_setup(), and schedule error recovery to reinitialize the controller.

Timeline

  1. CVE published
  2. Record last updated

Affected versions

  • Linux Linux

    From 5.15.181 · fixed in 5.15.224; From 6.1.136 · fixed in 6.1.191; From 6.6.89 · fixed in 6.6.160; From 6.12.26 · fixed in 6.12.113; From 5.4.293 · fixed in 5.5; From 5.10.237 · fixed in 5.11; From 6.14.5 · fixed in 6.15

  • Linux Linux

    6.15

  • KernelLinux

    fixed in 6.6.160; From 6.7.0 · fixed in 6.12.113; From 6.13.0 · fixed in 6.18.56; From 6.15.0 · fixed in 7.2.10

References 7

git.kernel.org