Live › vulnerability › CVE-2026-98767
Go to dashboardIn the Linux kernel's DWC3 USB gadget driver, a GEVNTCOUNT value larger than the event buffer makes the handler return without clearing the interrupt, so the level-triggered line keeps firing until the kernel panics. The sources describe a local-register write reproducer (devmem to GEVNTCOUNT), so the realistic impact is a denial of service.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Only systems that run a kernel with the commit 63ccd26cd1f6 and use a DWC3 USB controller are exposed, which mostly means embedded boards, ARM SoCs and some development hardware. Standard x86 servers and cloud VMs without a DWC3 controller are not affected, and the sources do not say which kernel versions carry the bug beyond that commit.
No product ranges from the sources yet.
uname -r to see the running kernel version, then compare it against the fixed kernel in the NVD entry for CVE-2026-98767lsmod | grep dwc3 or dmesg | grep -i dwc3Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98767")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.