CVE-2026-98767 json
usb: dwc3: gadget: fix IRQ storm on invalid event buffer count
published 24d ago modified 12d ago also EUVD-2026-103852
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
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.
Patch / fix
- Linux Linux 5.5, 5.11, 5.15.224, 6.1.191, 6.6.160, 6.12.113, 6.15, 7.3
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.10-1
- linux-6.12 Debian 12 6.12.113-1~deb12u1
debian advisories DEBIAN-CVE-2026-98767
- linux Ubuntu 24.04 LTS 6.8.0-149.149
- linux Ubuntu 26.04 LTS 7.0.0-43.43
- linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
- linux-aws Ubuntu 26.04 LTS 7.0.0-1017.18
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1017.19
- linux-gke Ubuntu 24.04 LTS 6.8.0-1068.77
- linux-gke Ubuntu 26.04 LTS 7.0.0-1010.11
ubuntu advisories UBUNTU-CVE-2026-98767
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/2c41e442ff6304532bf369aa618b23c8a474feb4 commit
- git.kernel.org/stable/c/86b9c867fb061a147df05ff0d9bb69dd3d79f49a commit
- git.kernel.org/stable/c/6cd82563bb270e03fe2f91324660ea14e3ce5d1a commit
- git.kernel.org/stable/c/96918ca25ff467c25675478fc79393df4ae9d74c commit
- git.kernel.org/stable/c/ba927133b301894e7d24099afbb701887c8cd2f1 commit
- git.kernel.org/stable/c/f51cadb02b439850ab411df0a2cf4288a66d42e2 commit
- git.kernel.org/stable/c/1ff77cbefe5a653ea12874c213ea4bd0d72c1067 commit
Is CVE-2026-98767 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-98767 updated cvss 5.1
kernel: usb: dwc3: gadget: fix IRQ storm on invalid event buffer count
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/2c41e442ff6304532bf369aa618b23c8a474feb4
- git.kernel.org /stable/c/86b9c867fb061a147df05ff0d9bb69dd3d79f49a
- git.kernel.org /stable/c/6cd82563bb270e03fe2f91324660ea14e3ce5d1a
- git.kernel.org /stable/c/96918ca25ff467c25675478fc79393df4ae9d74c
- git.kernel.org /stable/c/ba927133b301894e7d24099afbb701887c8cd2f1
- git.kernel.org /stable/c/f51cadb02b439850ab411df0a2cf4288a66d42e2
- git.kernel.org /stable/c/1ff77cbefe5a653ea12874c213ea4bd0d72c1067
Sources
- CVE List CVE-2026-98767
- NVD CVE-2026-98767
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.