Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-98762 Overview
CVE-2026-98762 is a use-after-free vulnerability in the Linux kernel's USB DWC2 (DesignWare USB 2.0) host controller driver. The flaw stems from improper ordering of timer teardown and host controller driver (HCD) state cleanup. The dwc2_wakeup_detected() callback accesses DWC2 host state and can rearm the wakeup timer, while dwc2_hcd_free() deletes the timer only after freeing host-owned state. Because timer_delete() does not synchronize with a running callback or prevent requeueing, the timer may fire against freed memory. Linux kernel maintainers resolved the issue by stopping and shutting down the timer in dwc2_hcd_release() before HCD resources are released.
Critical Impact
A race between the DWC2 wakeup timer callback and HCD teardown can trigger a use-after-free in kernel memory, leading to potential kernel memory corruption or denial of service on systems using DWC2 USB host controllers.
Affected Products
- Linux kernel versions containing the DWC2 USB host driver prior to the fix
- Platforms using DesignWare USB 2.0 (DWC2) host controllers (common on Raspberry Pi and various ARM SoCs)
- Stable kernel branches patched via commits 4333174, 441be31, 79ba37d, 82cc242, and fd772af
Discovery Timeline
- 2026-10-18 - CVE-2026-98762 published to the National Vulnerability Database
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-98762
Vulnerability Analysis
The vulnerability resides in the DWC2 USB host controller driver (drivers/usb/dwc2/) in the Linux kernel. The driver registers a wakeup timer whose callback, dwc2_wakeup_detected(), inspects DWC2 host state and can re-schedule itself. During teardown, dwc2_hcd_free() invoked timer_delete() on the wakeup timer only after releasing host-owned resources. timer_delete() neither waits for an in-flight timer callback to finish nor prevents the callback from re-queueing the timer. As a result, the callback can run or be re-armed against already-freed state, producing a classic use-after-free in kernel context [CWE-416].
Root Cause
The root cause is incorrect lifecycle ordering between timer cancellation and resource deallocation. Using timer_delete() instead of a synchronous variant such as timer_shutdown_sync() leaves a window in which the timer callback can execute concurrently with cleanup, access freed state, and arm the timer again.
Attack Vector
Triggering the race requires exercising the DWC2 driver teardown path, either through HCD initialization failure or normal device removal, while a USB wakeup event causes the timer to fire. The condition is primarily reachable by local actors with the ability to influence USB device presence or power states, or during module unload. No remote network vector is identified.
No verified public exploit code is available. For technical details of the fix, see the Linux Kernel Commit 4333174 and the Linux Kernel Commit fd772af.
Detection Methods for CVE-2026-98762
Indicators of Compromise
- Kernel oops or panic messages referencing dwc2_wakeup_detected, dwc2_hcd_free, or dwc2_hcd_release in dmesg or /var/log/kern.log
- KASAN (Kernel Address Sanitizer) reports flagging use-after-free in DWC2 timer code paths
- Unexpected USB host controller resets or device removal events coinciding with system instability
Detection Strategies
- Audit installed kernel versions against the fixed stable commits (4333174, 441be31, 79ba37d, 82cc242, fd772af) using package inventory tooling
- Enable KASAN or kernel lockdep instrumentation in test environments running DWC2 hardware to surface the race during stress testing
- Correlate USB subsystem logs with kernel crash telemetry on affected ARM/embedded platforms
Monitoring Recommendations
- Collect dmesg and journald kernel logs centrally and alert on DWC2-related oops signatures
- Track kernel version drift across fleets of embedded or ARM-based endpoints that commonly ship with DWC2 controllers
- Monitor for abnormal reboot patterns on devices that use USB wakeup functionality
How to Mitigate CVE-2026-98762
Immediate Actions Required
- Identify systems running vulnerable Linux kernels with the DWC2 driver loaded (lsmod | grep dwc2)
- Schedule kernel updates to stable releases that include the referenced upstream commits
- Prioritize patching for embedded and single-board computer deployments where DWC2 is standard
Patch Information
The fix moves timer shutdown into dwc2_hcd_release() so the wakeup timer is stopped before HCD state is freed, covering both the initialization error path and normal removal. Patches are available in multiple stable branches: Linux Kernel Commit 441be31, Linux Kernel Commit 79ba37d, Linux Kernel Commit 82cc242, and Linux Kernel Commit fd772af. Apply the vendor-supplied kernel update from your distribution.
Workarounds
- Where feasible, avoid unloading or reinitializing the dwc2 module on production systems until patched
- Disable USB remote wakeup on affected controllers to reduce the likelihood of the timer firing during teardown
- Restrict physical and local access to devices using DWC2 host controllers while patches are being rolled out
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

