CVE-2025-37882

Advisory lineage Upstream: 0 Downstream: 12
Analyzed
Published: 09 May 2025, 06:45
Last modified:11 May 2026, 21:16

Vulnerability Summary

Overall Risk (default)
medium
31/100
CVSS Score
7.8 HIGH
v3.1 (nvd)
EPSS Score
0.04% LOW
0% probability +0.03%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

09 May 2025, 06:45
Published
Vulnerability first disclosed
11 May 2026, 21:16
Last Modified
Vulnerability information updated

Description

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.

CVSS Metrics

  • v3.1•HIGH•Score: 7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Trends

Current EPSS score: 0.04%• Percentile: 13%

Techniques & Countermeasures

  • CWE-416•Use After Free

    The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Affected Systems

  • linux•linux

    ≥ 608b973b70f87e9a9bafbfdfa16aab68507aef45, < 16a7a8e6c47fea5c847beb696c8c21a7a44c1915 | ≥ 608b973b70f87e9a9bafbfdfa16aab68507aef45, < 39a080a2925c81b0f1da0add44722ef2b78e5454 | ≥ 608b973b70f87e9a9bafbfdfa16aab68507aef45, < 906dec15b9b321b546fd31a3c99ffc13724c7af4 | 6.10

  • linux•linux_kernel

    < 6.12.26 | ≥ 6.13, < 6.14.5

References (3)