LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22022: usb: xhci: Apply the link chain quirk on NEC isoc endpoints

In the Linux kernel, the following vulnerability has been resolved: usb: xhci: Apply the link chain quirk on NEC isoc endpoints Two clearly different specimens of NEC uPD720200 (one with start/stop bug, one without) were seen to cause IOMMU faults after some Missed Service Errors. Faulting address is immediately after a transfer ring segment and patched dynamic debug messages revealed that the MSE was received when waiting for a TD near the end of that segment: [ 1.041954] xhci_hcd: Miss service interval error for slot 1 ep 2 expected TD DMA ffa08fe0 [ 1.042120] xhci_hcd: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffa09000 flags=0x0000] [ 1.042146] xhci_hcd: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffa09040 flags=0x0000] It gets even funnier if the next page is a ring segment accessible to the HC. Below, it reports MSE in segment at ff1e8000, plows through a zero-filled page at ff1e9000 and starts reporting events for TRBs in page at ff1ea000 every microframe, instead of jumping to seg ff1e6000. [ 7.041671] xhci_hcd: Miss service interval error for slot 1 ep 2 expected TD DMA ff1e8fe0 [ 7.041999] xhci_hcd: Miss service interval error for slot 1 ep 2 expected TD DMA ff1e8fe0 [ 7.042011] xhci_hcd: WARN: buffer overrun event for slot 1 ep 2 on endpoint [ 7.042028] xhci_hcd: All TDs skipped for slot 1 ep 2. Clear skip flag. [ 7.042134] xhci_hcd: WARN: buffer overrun event for slot 1 ep 2 on endpoint [ 7.042138] xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 31 [ 7.042144] xhci_hcd: Looking for event-dma 00000000ff1ea040 trb-start 00000000ff1e6820 trb-end 00000000ff1e6820 [ 7.042259] xhci_hcd: WARN: buffer overrun event for slot 1 ep 2 on endpoint [ 7.042262] xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 31 [ 7.042266] xhci_hcd: Looking for event-dma 00000000ff1ea050 trb-start 00000000ff1e6820 trb-end 00000000ff1e6820 At some point completion events change from Isoch Buffer Overrun to Short Packet and the HC finally finds cycle bit mismatch in ff1ec000. [ 7.098130] xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 7.098132] xhci_hcd: Looking for event-dma 00000000ff1ecc50 trb-start 00000000ff1e6820 trb-end 00000000ff1e6820 [ 7.098254] xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 7.098256] xhci_hcd: Looking for event-dma 00000000ff1ecc60 trb-start 00000000ff1e6820 trb-end 00000000ff1e6820 [ 7.098379] xhci_hcd: Overrun event on slot 1 ep 2 It's possible that data from the isochronous device were written to random buffers of pending TDs on other endpoints (either IN or OUT), other devices or even other HCs in the same IOMMU domain. Lastly, an error from a different USB device on another HC. Was it caused by the above? I don't know, but it may have been. The disk was working without any other issues and generated PCIe traffic to starve the NEC of upstream BW and trigger those MSEs. The two HCs shared one x1 slot by means of a commercial "PCIe splitter" board. [ 7.162604] usb 10-2: reset SuperSpeed USB device number 3 using xhci_hcd [ 7.178990] sd 9:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s [ 7.179001] sd 9:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 04 02 ae 00 00 02 00 00 [ 7.179004] I/O error, dev sdb, sector 67284480 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 0 Fortunately, it appears that this ridiculous bug is avoided by setting the chain bit of Link TRBs on isochronous rings. Other ancient HCs are known which also expect the bit to be set and they ignore Link TRBs if it's not. Reportedly, 0.95 spec guaranteed that the bit is set. The bandwidth-starved NEC HC running a 32KB/uframe UVC endpoint reports tens of MSEs per second and runs into the bug within seconds. Chaining Link TRBs allows the same workload to run for many minutes, many times. No ne ---truncated---

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-22022 is a Linux kernel USB xHCI issue tied to NEC uPD720200 controllers handling isochronous endpoints, such as high-bandwidth video devices. Under missed service errors, the controller may read past a transfer ring segment, causing IOMMU faults and possible incorrect buffer writes. Exposure is hardware-specific and not broadly internet-facing.

Executive priority

Treat this as targeted infrastructure hygiene rather than an emergency internet-wide issue. Prioritize patching systems with NEC uPD720200 USB controllers in operational, appliance, media, lab, or workstation environments where USB device reliability and data integrity matter.

Technical view

The Linux xHCI driver did not apply a link-chain quirk to NEC isochronous rings. The source describes missed service errors near segment ends, followed by IOMMU faults, buffer overrun events, and transfer events outside the current TD. The kernel fix sets the chain bit on Link TRBs for affected isochronous rings.

Likely exposure

Likely exposure is limited to Linux systems using NEC uPD720200 xHCI USB host controllers with isochronous USB devices, especially bandwidth-heavy UVC devices. Servers, workstations, kiosks, or appliances with these controllers deserve review. Systems without this hardware path are unlikely to be affected based on the provided sources.

Exploitation context

The bundle does not show active exploitation, and KEV is false. The described trigger involves bandwidth-starved NEC hardware, missed service errors, and specific USB transfer conditions. This looks more like local hardware-triggered kernel memory or I/O corruption risk than a remote network exposure.

Researcher notes

Evidence is strongest for NEC uPD720200 behavior under missed service errors on isochronous endpoints. The source explicitly says random buffer writes are possible, but does not prove exploitability or privilege impact. No CVSS, CWE, or active exploitation evidence is included in the bundle.

Mitigation direction

  • Update Linux kernels to versions containing the referenced stable fixes.
  • Check distribution vendor guidance for backported kernel fixes.
  • Prioritize hosts with NEC uPD720200 controllers and high-bandwidth USB devices.
  • Temporarily reduce or remove risky isochronous USB workloads where practical.
  • Avoid assuming non-upstream kernels are fixed without vendor confirmation.

Validation and detection

  • Inventory Linux hosts for NEC uPD720200 xHCI USB controllers.
  • Identify attached isochronous USB devices, especially UVC cameras.
  • Confirm the running kernel includes one referenced stable commit or vendor backport.
  • Review logs for xhci_hcd missed service errors and IOMMU faults.
  • Track affected kernel versions against distribution security advisories.
Prepared
Confidence
medium
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-22022 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7e393a834b41001174a8fb3ae3bc23a749467760, 7e393a834b41001174a8fb3ae3bc23a749467760, 7e393a834b41001174a8fb3ae3bc23a749467760, 7e393a834b41001174a8fb3ae3bc23a749467760, 7e393a834b41001174a8fb3ae3bc23a749467760, 7e393a834b41001174a8fb3ae3bc23a749467760, 7e393a834b41001174a8fb3ae3bc23a749467760, 7e393a834b41001174a8fb3ae3bc23a749467760, 5c7a6982e976b381595c9d4ee8e8c94564a40aec, f12ea4a8ca7009fa2d54794c3fcb8e638453bcff, 3.0.9, 3.1.1unaffected
LinuxLinux3.2, 0, 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.22, 6.13.10, 6.14.1, 6.15affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.