CVE-2026-98767: usb: dwc3: gadget: fix IRQ storm on invalid event buffer count
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 1ff77cbefe5a653ea12874c213ea4bd0d72c1067, 2c41e442ff6304532bf369aa618b23c8a474feb4, 5.11; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
Low priority for now. Upgrade to Linux Linux 1ff77cbefe5a653ea12874c213ea4bd0d72c1067, 2c41e442ff6304532bf369aa618b23c8a474feb4, 5.11; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 18, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 015c39f38e69a491d2abd5e98869a500a9459b3b, b43225948b231b3f331194010f84512bee4d9f59, 99d655119b870ee60e4dbf310aa9a1ed8d9ede3d, 6.15affected
- c0079630f268843a25ed75226169cba40e0d8880 and later · before 2c41e442ff6304532bf369aa618b23c8a474feb4affected · git
- a44547015287a19001384fe94dbff84c92ce4ee1 and later · before 86b9c867fb061a147df05ff0d9bb69dd3d79f49aaffected · git
- c4d80e41cb42008dceb35e5dbf52574d93beac0d and later · before 6cd82563bb270e03fe2f91324660ea14e3ce5d1aaffected · git
- 52a7c9d930b95aa8b1620edaba4818040c32631f and later · before 96918ca25ff467c25675478fc79393df4ae9d74caffected · git
- 63ccd26cd1f6600421795f6ca3e625076be06c9f and later · before ba927133b301894e7d24099afbb701887c8cd2f1affected · git
- 63ccd26cd1f6600421795f6ca3e625076be06c9f and later · before f51cadb02b439850ab411df0a2cf4288a66d42e2affected · git
- 63ccd26cd1f6600421795f6ca3e625076be06c9f and later · before 1ff77cbefe5a653ea12874c213ea4bd0d72c1067affected · git
- 5.15.181 and later · before 5.15.224affected · semver
- 6.1.136 and later · before 6.1.191affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.10-1 | 7.2.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98765Oct 18, 2026 · USB: gadget: dummy-hcd: Fix wait for outstanding request completions0Monitor
- ← EarlierCVE-2026-98766Oct 18, 2026 · usb: gadget: aspeed-vhub: cancel wake work on device removal0Monitor
- Later →CVE-2026-98768Oct 18, 2026 · usb: typec: anx7411 - stop the IRQ before destroying the workqueue0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1ff77cbefe5a653ea12874c213ea4bd0d72c1067 | Vendor (CNA) |
| Linux Linux | 2c41e442ff6304532bf369aa618b23c8a474feb4 | Vendor (CNA) |
| Linux Linux | 5.11 | Vendor (CNA) |
| Linux Linux | 5.15.224 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 6.1.191 | Vendor (CNA) |
| Linux Linux | 6.12.113 | Vendor (CNA) |
| Linux Linux | 6.15 | Vendor (CNA) |
| Linux Linux | 6.6.160 | Vendor (CNA) |
| Linux Linux | 6cd82563bb270e03fe2f91324660ea14e3ce5d1a | Vendor (CNA) |
| Linux Linux | 86b9c867fb061a147df05ff0d9bb69dd3d79f49a | Vendor (CNA) |
| Linux Linux | 96918ca25ff467c25675478fc79393df4ae9d74c | Vendor (CNA) |
| Linux Linux | ba927133b301894e7d24099afbb701887c8cd2f1 | Vendor (CNA) |
| Linux Linux | f51cadb02b439850ab411df0a2cf4288a66d42e2 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.159.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 6, 2026+19 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/2c41e442ff6304532bf369aa618b23c8a474feb4
- git.kernel.org/stable/c/6cd82563bb270e03fe2f91324660ea14e3ce5d1a
- git.kernel.org/stable/c/86b9c867fb061a147df05ff0d9bb69dd3d79f49a
- git.kernel.org/stable/c/96918ca25ff467c25675478fc79393df4ae9d74c
- git.kernel.org/stable/c/ba927133b301894e7d24099afbb701887c8cd2f1
- git.kernel.org/stable/c/f51cadb02b439850ab411df0a2cf4288a66d42e2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.