CVE-2025-22022

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-04-16. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2025-11377 (ENISA EUVD) · GHSA-4j7f-c5p6-h9j2 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
9th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 16, 2025

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Jul 30, 2026
Patch available.
Web page

usb: xhci: Apply the link chain quirk on NEC isoc endpoints - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dbf427663ce272070d3004b5fca63a4a537d781c
Web page

usb: xhci: Apply the link chain quirk on NEC isoc endpoints - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bb0ba4cb1065e87f9cc75db1fa454e56d0894d01
Web page

usb: xhci: Apply the link chain quirk on NEC isoc endpoints - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/abf2df229b6a9172cc1827749c1a446d28e00a2e
Web page

usb: xhci: Apply the link chain quirk on NEC isoc endpoints - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a4931d9fb99eb5462f3eaa231999d279c40afb21
Web page

usb: xhci: Apply the link chain quirk on NEC isoc endpoints - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8b586de6f03c850ff48d42e539b4708d1f3f8f1a
Web page

usb: xhci: Apply the link chain quirk on NEC isoc endpoints - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/43a18225150ce874d23b37761c302a5dffee1595
Web page

usb: xhci: Apply the link chain quirk on NEC isoc endpoints - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1143f790a6316201dc8f067eba4c94ea97ecb6ca
Web page

usb: xhci: Apply the link chain quirk on NEC isoc endpoints - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/061a1683bae6ef56ab8fa392725ba7495515cd1d

Vendor Advisories for CVE-2025-22022(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-22.22) @ plucky2026-10-27ubuntu
ubuntulinux-tools-azure (6.14.0-1007.7) @ plucky2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-28.28) @ oracular2026-10-27ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1024.24) @ noble2026-10-27ubuntu
ubuntulinux-tools-lowlatency-64k (6.11.0-1015.16) @ oracular2026-10-27ubuntu
ubuntulinux-tools-oracle-64k (6.14.0-1007.7) @ plucky2026-10-27ubuntu
ubuntulinux-tools-azure-6.11 (6.11.0-1018.18) @ oracular2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1067 (5.15.0-1067.71) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1103.93) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1102.106) @ jammy2026-10-27ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1094.98) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.173.183~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1097.95) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1044.46) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-110.110) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1047.48) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1051.54.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1054.57+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1052.56) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1054.60) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1054.57~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1054.60+fips1) @ noble2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1059.65~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1022.22) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-64k-6.8 (6.8.0-1051.54) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1049.50) @ noble2026-10-27ubuntu
linuxKernel @ 5.10.248 (fixes >=3.2.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (48 versions)
  • every version up to 5.10.249-1: fixed in 5.10.249-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.159-1~deb11u1 (14 versions)
  • every version up to 6.1.162-1~deb11u1: fixed in 6.1.162-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (46 versions)
  • every version up to 6.1.162-1: fixed in 6.1.162-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.22-1: fixed in 6.12.22-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.22-1: fixed in 6.12.22-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 202 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 106 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:42 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  4. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  8. 2026-10-27 12:38 UTCEG score recompute
  9. 2026-10-27 12:38 UTCVendor advisory
  10. 2026-10-27 12:37 UTCGHSA enrichmentGHSA-4j7f-c5p6-h9j2 · GitHub severity HIGH · GitHub CVSS 7.8
  11. 2026-10-25 16:42 UTCEG score recompute
  12. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-10-22 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-10-19 00:41 UTCEG score recompute
  20. 2026-10-19 00:41 UTCVendor advisory
  21. 2026-10-19 00:41 UTCGHSA enrichmentGHSA-4j7f-c5p6-h9j2 · GitHub severity HIGH · GitHub CVSS 7.8
  22. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-10-18 05:45 UTCEG score recompute
  24. 2026-10-17 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-10-16 16:38 UTCEPSS rescoreEPSS 0.2% · 9th percentile
Show 71 more
  1. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  3. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  4. 2026-10-12 17:19 UTCEG score recompute
  5. 2026-10-11 20:51 UTCEG score recompute
  6. 2026-10-11 19:01 UTCEG score recompute
  7. 2026-10-11 15:41 UTCEG score recompute
  8. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  15. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-10-02 16:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  18. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  19. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  20. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  21. 2026-09-27 03:45 UTCOSV refresh
  22. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  24. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  26. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  27. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  28. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  29. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  30. 2026-09-16 05:13 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  31. 2026-09-15 03:09 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  32. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  33. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  34. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  35. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  36. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  37. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  38. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  39. 2026-09-07 12:48 UTCOSV refresh
  40. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  41. 2026-09-05 15:28 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  42. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  43. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  44. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  45. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  46. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  47. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  48. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  49. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  50. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  51. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  52. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  53. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  54. 2026-08-20 22:01 UTCOSV refresh
  55. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  56. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  57. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  58. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  59. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  60. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  61. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  62. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  63. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  64. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  65. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  66. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  67. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  68. 2026-08-05 13:59 UTCEG score recompute
  69. 2026-08-05 13:59 UTCVendor advisory
  70. 2026-08-05 13:59 UTCGHSA enrichmentGHSA-4j7f-c5p6-h9j2 · GitHub severity HIGH · GitHub CVSS 7.8
  71. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.2% · 8th percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-22022?
CVE-2025-22022 is a high-severity vulnerability; its CVE record was published on April 16, 2025. 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…
When was the CVE record for CVE-2025-22022 published?
The CVE record for CVE-2025-22022 was published on April 16, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2025-22022 actively exploited?
CVE-2025-22022 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-22022?
CVE-2025-22022 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-22022?
A fix for CVE-2025-22022 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-22022 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-22022

Explore →

Is Your Infrastructure Affected by CVE-2025-22022?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs