CVE-2026-43250

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

usb: chipidea: udc: fix DMA and SG cleanup in _ep_nuke()

The ChipIdea UDC driver can encounter "not page aligned sg buffer" errors when a USB device is reconnected after being disconnected during an active transfer. This occurs because _ep_nuke() returns requests to the gadget layer without properly unmapping DMA buffers or cleaning up scatter-gather bounce buffers.

Root cause: When a disconnect happens during a multi-segment DMA transfer, the request's num_mapped_sgs field and sgt.sgl pointer remain set with stale values. The request is returned to the gadget driver with status -ESHUTDOWN but still has active DMA state. If the gadget driver reuses this request on reconnect without reinitializing it, the stale DMA state causes _hardware_enqueue() to skip DMA mapping (seeing non-zero num_mapped_sgs) and attempt to use freed/invalid DMA addresses, leading to alignment errors and potential memory corruption.

The normal completion path via _hardware_dequeue() properly calls usb_gadget_unmap_request_by_dev() and sglist_do_debounce() before returning the request. The _ep_nuke() path must do the same cleanup to ensure requests are returned in a clean, reusable state.

Fix: Add DMA unmapping and bounce buffer cleanup to _ep_nuke() to mirror the cleanup sequence in _hardware_dequeue():

  • Call usb_gadget_unmap_request_by_dev() if num_mapped_sgs is set
  • Call sglist_do_debounce() with copy=false if bounce buffer exists

This ensures that when requests are returned due to endpoint shutdown, they don't retain stale DMA mappings. The 'false' parameter to sglist_do_debounce() prevents copying data back (appropriate for shutdown path where transfer was aborted).

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 6, 2026

Last Modified

May 12, 2026

Advisory Details (4)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

usb: chipidea: udc: fix DMA and SG cleanup in _ep_nuke() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f4fbf2d4750d12ac8525d2efac1016fa0d84d4ec
generic

usb: chipidea: udc: fix DMA and SG cleanup in _ep_nuke() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e74c436f8568af1c60942469d0a2300b3ada3857
generic

usb: chipidea: udc: fix DMA and SG cleanup in _ep_nuke() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cea2a1257a3b5ea3e769a445b34af13e6aa5a123
generic

usb: chipidea: udc: fix DMA and SG cleanup in _ep_nuke() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b72b834511d17f4d069d512f78671f3f210a2f1

Vendor Advisories for CVE-2026-43250(1)

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

Patch Availability(13)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (113 versions)6.19.6-1

Weakness Classification(1)

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

All Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 5× in last 7d / 72× 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 208 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43250?
CVE-2026-43250 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: usb: chipidea: udc: fix DMA and SG cleanup in epnuke() The ChipIdea UDC driver can encounter "not page aligned sg buffer" errors when a USB device is reconnected after being disconnected during an active transfer. This occurs…
When was CVE-2026-43250 disclosed?
CVE-2026-43250 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on May 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43250 actively exploited?
CVE-2026-43250 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 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-43250?
CVE-2026-43250 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43250?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43250, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43250

Explore →

Is Your Infrastructure Affected by CVE-2026-43250?

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