CVE-2025-21916

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-04-01. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

usb: atm: cxacru: fix a flaw in existing endpoint checks

Syzbot once again identified a flaw in usb endpoint checking, see [1]. This time the issue stems from a commit authored by me (2eabb655a968 ("usb: atm: cxacru: fix endpoint checking in cxacru_bind()")).

While using usb_find_common_endpoints() may usually be enough to discard devices with wrong endpoints, in this case one needs more than just finding and identifying the sufficient number of endpoints of correct types - one needs to check the endpoint's address as well.

Since cxacru_bind() fills URBs with CXACRU_EP_CMD address in mind, switch the endpoint verification approach to usb_check_XXX_endpoints() instead to fix incomplete ep testing.

[1] Syzbot report: usb 5-1: BOGUS urb xfer, pipe 3 != type 1 WARNING: CPU: 0 PID: 1378 at drivers/usb/core/urb.c:504 usb_submit_urb+0xc4e/0x18c0 drivers/usb/core/urb.c:503 ... RIP: 0010:usb_submit_urb+0xc4e/0x18c0 drivers/usb/core/urb.c:503 ... Call Trace: cxacru_cm+0x3c8/0xe50 drivers/usb/atm/cxacru.c:649 cxacru_card_status drivers/usb/atm/cxacru.c:760 [inline] cxacru_bind+0xcf9/0x1150 drivers/usb/atm/cxacru.c:1223 usbatm_usb_probe+0x314/0x1d30 drivers/usb/atm/usbatm.c:1058 cxacru_usb_probe+0x184/0x220 drivers/usb/atm/cxacru.c:1377 usb_probe_interface+0x641/0xbb0 drivers/usb/core/driver.c:396 really_probe+0x2b9/0xad0 drivers/base/dd.c:658 __driver_probe_device+0x1a2/0x390 drivers/base/dd.c:800 driver_probe_device+0x50/0x430 drivers/base/dd.c:830 ...

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

April 1, 2025

Last Modified

November 3, 2025

References (10)

Patch Availability(31)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.140.135) @ jammy2026-05-30ubuntu
ubuntulinux-tools-fips (5.15.0.140.80) @ jammy2026-05-30ubuntu
ubuntulinux-tools-gcp-lts-22.04 (5.15.0.1083.79) @ jammy2026-05-30ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1064 (5.4.0-1064.68) @ focal2026-05-30ubuntu
ubuntulinux-tools-gcp-fips (5.15.0.1083.73) @ jammy2026-05-30ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.216.208) @ focal2026-05-30ubuntu
ubuntulinux-tools-nvidia-tegra-rt (5.15.0.1037.37) @ jammy2026-05-30ubuntu
ubuntulinux-tools-gcp-fips (5.4.0.1149.91) @ focal2026-05-30ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1083.92~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-tools-azure-fips (5.4.0.1151.88) @ focal2026-05-30ubuntu
ubuntulinux-tools-realtime (5.15.0.1084.88) @ jammy2026-05-30ubuntu
ubuntulinux-tools-kvm (5.4.0.1133.129) @ focal2026-05-30ubuntu
ubuntulinux-tools-oracle-edge (5.4.0.1144.154~18.04.1) @ bionic2026-05-30ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.142.152~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1050.54) @ jammy2026-05-30ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1084.91~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1078.76) @ jammy2026-05-30ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.216.236~18.04.1) @ bionic2026-05-30ubuntu
ubuntulinux-tools-ibm-lts-20.04 (5.4.0.1092.121) @ focal2026-05-30ubuntu
ubuntulinux-tools-bluefield (5.4.0.1105.101) @ focal2026-05-30ubuntu
ubuntulinux-tools-azure-fips (5.15.0.1089.74) @ jammy2026-05-30ubuntu
ubuntulinux-tools-aws-fips (5.15.0.1084.80) @ jammy2026-05-30ubuntu
ubuntulinux-tools-ibm-edge (5.4.0.1092.97~18.04.1) @ bionic2026-05-30ubuntu
ubuntulinux-tools-gke-5.15 (5.15.0.1081.80) @ jammy2026-05-30ubuntu
ubuntulinux-tools-azure-6.11 (6.11.0-1018.18) @ oracular2026-05-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1039.42.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1129.160) @ focal2026-05-30ubuntu
ubuntulinux-tools-lowlatency-64k (6.11.0-1015.16) @ oracular2026-05-30ubuntu
ubuntulinux-tools-aws-lts-20.04 (5.4.0.1146.143) @ focal2026-05-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-84.84) @ noble2026-05-30ubuntu
linuxKernel @ 5.4.291—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.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 107 total refreshes for this CVE.

  1. 2026-08-07 16:26 UTCEPSS rescore
  2. 2026-08-06 13:46 UTCEPSS rescore
  3. 2026-08-05 19:16 UTCEPSS rescore
  4. 2026-08-04 15:09 UTCEPSS rescore
  5. 2026-08-04 10:37 UTCEPSS rescore
  6. 2026-08-03 10:35 UTCEPSS rescore
  7. 2026-08-02 02:25 UTCEPSS rescore
  8. 2026-07-30 16:27 UTCEPSS rescore
  9. 2026-07-30 01:29 UTCEPSS rescore
  10. 2026-07-28 15:35 UTCEPSS rescore
  11. 2026-07-27 14:12 UTCEPSS rescore
  12. 2026-07-26 14:53 UTCEPSS rescore
  13. 2026-07-25 14:17 UTCEPSS rescore
  14. 2026-07-24 14:17 UTCEPSS rescore
  15. 2026-07-24 10:11 UTCOSV refresh
  16. 2026-07-23 14:17 UTCEPSS rescore
  17. 2026-07-23 02:50 UTCEG score recompute
  18. 2026-07-22 14:07 UTCEPSS rescore
  19. 2026-07-22 14:07 UTCEPSS rescore
  20. 2026-07-21 15:24 UTCEPSS rescore
  21. 2026-07-20 17:07 UTCEPSS rescore
  22. 2026-07-19 14:30 UTCEPSS rescore
  23. 2026-07-19 14:30 UTCEPSS rescore
  24. 2026-07-19 02:28 UTCEPSS rescore
  25. 2026-07-19 02:28 UTCEPSS rescore
Show 75 more
  1. 2026-07-18 10:03 UTCEPSS rescore
  2. 2026-07-16 17:02 UTCEPSS rescore
  3. 2026-07-15 01:59 UTCEPSS rescore
  4. 2026-07-13 22:29 UTCEPSS rescore
  5. 2026-07-13 22:29 UTCEPSS rescore
  6. 2026-07-13 06:12 UTCEPSS rescore
  7. 2026-07-13 06:12 UTCEPSS rescore
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-12 05:46 UTCEPSS rescore
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-11 08:26 UTCEPSS rescore
  12. 2026-07-09 19:09 UTCEPSS rescore
  13. 2026-07-08 15:14 UTCEPSS rescore
  14. 2026-07-07 13:45 UTCEPSS rescore
  15. 2026-07-07 05:51 UTCOSV refresh
  16. 2026-07-06 16:26 UTCEPSS rescore
  17. 2026-07-06 02:22 UTCEPSS rescore
  18. 2026-07-06 02:22 UTCEPSS rescore
  19. 2026-07-05 02:30 UTCEPSS rescore
  20. 2026-07-04 06:30 UTCEPSS rescore
  21. 2026-07-01 15:06 UTCEPSS rescore
  22. 2026-06-30 23:21 UTCEPSS rescore
  23. 2026-06-30 23:21 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-28 14:07 UTCEPSS rescore
  26. 2026-06-28 14:07 UTCEPSS rescore
  27. 2026-06-28 04:55 UTCEPSS rescore
  28. 2026-06-28 04:55 UTCEPSS rescore
  29. 2026-06-27 03:08 UTCEPSS rescore
  30. 2026-06-27 03:08 UTCEPSS rescore
  31. 2026-06-25 13:49 UTCEPSS rescore
  32. 2026-06-25 13:49 UTCEPSS rescore
  33. 2026-06-24 14:04 UTCEPSS rescore
  34. 2026-06-24 14:04 UTCEPSS rescore
  35. 2026-06-23 21:32 UTCEPSS rescore
  36. 2026-06-23 21:32 UTCEPSS rescore
  37. 2026-06-22 14:25 UTCEPSS rescore
  38. 2026-06-22 14:25 UTCEPSS rescore
  39. 2026-06-21 14:56 UTCEPSS rescore
  40. 2026-06-21 14:56 UTCEPSS rescore
  41. 2026-06-21 01:59 UTCEPSS rescore
  42. 2026-06-21 01:59 UTCEPSS rescore
  43. 2026-06-19 19:25 UTCEPSS rescore
  44. 2026-06-19 19:25 UTCEPSS rescore
  45. 2026-06-18 17:52 UTCEPSS rescore
  46. 2026-06-18 17:52 UTCEPSS rescore
  47. 2026-06-18 17:05 UTCOSV refresh
  48. 2026-06-17 17:52 UTCEPSS rescore
  49. 2026-06-16 17:52 UTCEPSS rescore
  50. 2026-06-16 17:52 UTCEPSS rescore
  51. 2026-06-15 17:48 UTCEPSS rescore
  52. 2026-06-14 23:17 UTCEPSS rescore
  53. 2026-06-13 22:59 UTCEPSS rescore
  54. 2026-06-12 23:11 UTCEPSS rescore
  55. 2026-06-11 13:59 UTCEPSS rescore
  56. 2026-06-10 22:18 UTCEPSS rescore
  57. 2026-06-10 13:22 UTCEPSS rescore
  58. 2026-06-08 14:16 UTCEPSS rescore
  59. 2026-06-08 14:16 UTCEPSS rescore
  60. 2026-06-07 15:24 UTCEPSS rescore
  61. 2026-06-07 15:24 UTCEPSS rescore
  62. 2026-06-06 13:47 UTCEPSS rescore
  63. 2026-06-06 13:47 UTCEPSS rescore
  64. 2026-06-05 22:46 UTCEPSS rescore
  65. 2026-06-05 22:46 UTCEPSS rescore
  66. 2026-06-05 06:10 UTCEPSS rescore
  67. 2026-06-05 06:10 UTCEPSS rescore
  68. 2026-06-04 13:11 UTCEPSS rescore
  69. 2026-06-04 13:11 UTCEPSS rescore
  70. 2026-06-02 20:12 UTCEPSS rescore
  71. 2026-06-02 20:12 UTCEPSS rescore
  72. 2026-06-01 13:51 UTCEPSS rescore
  73. 2026-06-01 13:51 UTCEPSS rescore
  74. 2026-05-31 22:30 UTCEPSS rescore
  75. 2026-05-31 22:30 UTCEPSS rescore

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2025-21916?
CVE-2025-21916 is a medium vulnerability published on April 1, 2025. In the Linux kernel, the following vulnerability has been resolved: usb: atm: cxacru: fix a flaw in existing endpoint checks Syzbot once again identified a flaw in usb endpoint checking, see [1]. This time the issue stems from a commit authored by me (2eabb655a968 ("usb: atm: cxacru: fix endpoint…
When was CVE-2025-21916 disclosed?
CVE-2025-21916 was first published in the National Vulnerability Database on April 1, 2025, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-21916 actively exploited?
CVE-2025-21916 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.3% of all scored CVEs.
What is the CVSS score of CVE-2025-21916?
CVE-2025-21916 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-21916?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-21916, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-21916

Explore →

Is Your Infrastructure Affected by CVE-2025-21916?

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

Start Free Scan →Browse All CVEs