Skip to main content

Linux EUVDEUVD-2026-103852

| CVE-2026-98767
2026-10-18 Linux GHSA-7v54-4578-623x
View
Monitor Track and reassess. Why: No CVSS yet + weak signal (CWE or non-zero EPSS).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisCVE.org

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.

Affected VersionsENISA

Linux 6.14.5 <6.15
Linux 6.15
Linux patch: 6.12.113
Linux patch: 0
Linux 52a7c9d930b95aa8b1620edaba4818040c32631f <96918ca25ff467c25675478fc79393df4ae9d74c
Linux a44547015287a19001384fe94dbff84c92ce4ee1
Linux 6.6.89 <6.7
Linux patch: 7.3-rc6
Linux 6.1.136 <6.2
Linux 63ccd26cd1f6600421795f6ca3e625076be06c9f <ba927133b301894e7d24099afbb701887c8cd2f1
Linux 5.10.237 <5.11
Linux 5.4.293 <5.5
Linux patch: 6.18.56
Linux 5.15.181 <5.16
Linux 99d655119b870ee60e4dbf310aa9a1ed8d9ede3d
Linux 6.12.26 <6.12.113
Linux 63ccd26cd1f6600421795f6ca3e625076be06c9f <f51cadb02b439850ab411df0a2cf4288a66d42e2
Linux 015c39f38e69a491d2abd5e98869a500a9459b3b
Linux 63ccd26cd1f6600421795f6ca3e625076be06c9f <1ff77cbefe5a653ea12874c213ea4bd0d72c1067
Linux c4d80e41cb42008dceb35e5dbf52574d93beac0d
Linux b43225948b231b3f331194010f84512bee4d9f59
Linux patch: 7.2.10
Linux c0079630f268843a25ed75226169cba40e0d8880

Affected Packages

euvd linux fix: 5.5, 5.11, 5.16, 6.2, 6.7, 6.12.113, 6.15

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Lifecycle Timeline

2
Patch available
Oct 18, 2026 - 17:19 EUVD
CVE Published
Oct 18, 2026 - 15:48 cve.org
UNKNOWN (no severity yet)

Threat Intelligence Overview

EPSS Score
0.2%
Top 94% exploitable
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity Not scored yet
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
No CVSS yet + weak signal (CWE or non-zero EPSS)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy