{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98767 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98767 is a denial of service vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98767 and fix it if it is affected.\n\nWhat it is: CVE-2026-98767 is a denial of service vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98767 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98767/ (Markdown: https://insights.sbomify.com/CVE-2026-98767/index.md)","id":"CVE-2026-98767","markdown":"https://insights.sbomify.com/CVE-2026-98767/index.md","name":"CVE-2026-98767","record":{"aliases":["AZL-108912","BELL-CVE-2026-98767","DEBIAN-CVE-2026-98767","GHSA-7v54-4578-623x","UBUNTU-CVE-2026-98767"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel USB driver","requires_auth":"high_privilege","summary":"A local attacker with high privileges can trigger a kernel panic via an IRQ storm in the DWC3 USB gadget driver by writing invalid values to hardware registers.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nusb: dwc3: gadget: fix IRQ storm on invalid event buffer count\n\nWhen dwc3_check_event_buf() reads a GEVNTCOUNT value exceeding the\nevent buffer length, commit 63ccd26cd1f6 (\"usb: dwc3: gadget: check\nthat event count does not exceed event buffer length\") returns IRQ_NONE\nwithout writing back GEVNTCOUNT. Since the DWC3 interrupt is\nlevel-triggered, the uncleared IRQ source keeps the line asserted,\ncausing a tight IRQ storm that accumulates 99,900 unhandled interrupts\nand triggers spurious.c:184 BUG -\u003e kernel panic.\n\nThe resulting call stack:\n  __report_bad_irq+0xac/0xc8\n  note_interrupt+0x340/0x468\n  handle_irq_event+0xac/0xc0\n  handle_fasteoi_irq+0x120/0x228\n  gic_handle_irq+0x68/0x108\n  ...\n  kernel BUG at kernel/irq/spurious.c:184\n\nTo reproduce, write a bogus value exceeding the event buffer length\ndirectly to the GEVNTCOUNT register:\n\n  devmem \u003cDWC3_BASE + 0xc40c\u003e 4 0x1004\n\nWrite the bogus count back to GEVNTCOUNT to clear the IRQ source,\nconsistent with the stale event clearing pattern in\ndwc3_event_buffers_setup(), and schedule error recovery to\nreinitialize the controller.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"usb: dwc3: gadget: fix IRQ storm on invalid event buffer count","id":"CVE-2026-98767","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"usb: typec: anx7411 - stop the IRQ before destroying the workqueue","id":"CVE-2026-98768"},"packages":[],"prev":{"headline":"usb: gadget: aspeed-vhub: cancel wake work on device removal","id":"CVE-2026-98766"},"products":["Linux"],"published":"2026-10-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A local attacker with high privileges can trigger a kernel panic via an IRQ storm in the DWC3 USB gadget driver by writing invalid values to hardware registers.","url":"https://insights.sbomify.com/CVE-2026-98767/"}