Answer in brief
CVE-2025-37882 records a High severity (CVSS 7.8) vulnerability in usb: xhci: Fix isochronous Ring Underrun/Overrun event handling. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=608b973b70f87e9a9bafbfdfa16aab68507aef45 <16a7a8e6c47fea5c847beb696c8c21a7a44c1915 || >=608b973b70f87e9a9bafbfdfa16aab68507aef45 <39a080a2925c81b0f1da0add44722ef2b78e5454 || >=608b973b70f87e9a9bafbfdfa16aab68507aef45 <906dec15b9b321b546fd31a3c99ffc13724c7af4 | 16a7a8e6c47fea5c847beb696c8c21a7a44c1915, 39a080a2925c81b0f1da0add44722ef2b78e5454, 906dec15b9b321b546fd31a3c99ffc13724c7af4 |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
May 9, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: usb: xhci: Fix isochronous Ring Underrun/Overrun event handling The TRB pointer of these events points at enqueue at the time of error occurrence on xHCI 1.1+ HCs or it's NULL on older ones. By the time we are handling the event, a new TD may be queued at this ring position. I can trigger this race by rising interrupt moderation to increase IRQ handling delay. Similar delay may occur naturally due to system load. If this ever happens after a Missed Service Error, missed TDs will be skipped and the new TD processed as if it matched the event. It could be given back prematurely, risking data loss or buffer UAF by the xHC. Don't complete TDs on xrun events and don't warn if queued TDs don't match the event's TRB pointer, which can be NULL or a link/no-op TRB. Don't warn if there are no queued TDs at all. Now that it's safe, also handle xrun events if the skip flag is clear. This ensures completion of any TD stuck in 'error mid TD' state right before the xrun event, which could happen if a driver submits a finite number of URBs to a buggy HC and then an error occurs on the last TD.
Quoted source text, attributed separately from HOL analysis.