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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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)
EPSS
2.9%
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.

Weakness Classification(1)

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

Data Freshness Timeline

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

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-13 22:30 UTCEPSS rescore
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-08 15:16 UTCEPSS rescore
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-01 15:06 UTCEPSS rescore
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-28 14:07 UTCEPSS rescore
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-27 03:08 UTCEPSS rescore
  17. 2026-06-25 13:49 UTCEPSS rescore
  18. 2026-06-25 13:49 UTCEPSS rescore
  19. 2026-06-24 14:05 UTCEPSS rescore
  20. 2026-06-23 21:33 UTCEPSS rescore
  21. 2026-06-22 14:25 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-21 14:56 UTCEPSS rescore
  24. 2026-06-21 14:56 UTCEPSS rescore
  25. 2026-06-21 01:59 UTCEPSS rescore
Show 75 more
  1. 2026-06-19 19:25 UTCEPSS rescore
  2. 2026-06-18 17:52 UTCEPSS rescore
  3. 2026-06-18 17:52 UTCEPSS rescore
  4. 2026-06-17 17:53 UTCEPSS rescore
  5. 2026-06-16 17:52 UTCEPSS rescore
  6. 2026-06-15 17:49 UTCEPSS rescore
  7. 2026-06-15 06:05 UTCEG score recompute
  8. 2026-06-15 06:04 UTCGHSA enrichment
  9. 2026-06-14 18:49 UTCEG score recompute
  10. 2026-06-14 18:48 UTCGHSA enrichment
  11. 2026-06-14 07:33 UTCEG score recompute
  12. 2026-06-14 07:33 UTCGHSA enrichment
  13. 2026-06-13 23:00 UTCEPSS rescore
  14. 2026-06-12 23:55 UTCEG score recompute
  15. 2026-06-12 23:55 UTCGHSA enrichment
  16. 2026-06-12 23:12 UTCEPSS rescore
  17. 2026-06-12 23:12 UTCEPSS rescore
  18. 2026-06-12 07:27 UTCEG score recompute
  19. 2026-06-12 07:26 UTCGHSA enrichment
  20. 2026-06-11 20:10 UTCEG score recompute
  21. 2026-06-11 20:10 UTCGHSA enrichment
  22. 2026-06-11 14:00 UTCEPSS rescore
  23. 2026-06-11 08:54 UTCEG score recompute
  24. 2026-06-11 08:54 UTCGHSA enrichment
  25. 2026-06-10 22:18 UTCEPSS rescore
  26. 2026-06-10 21:31 UTCEG score recompute
  27. 2026-06-10 21:31 UTCGHSA enrichment
  28. 2026-06-10 13:22 UTCEPSS rescore
  29. 2026-06-10 13:22 UTCEPSS rescore
  30. 2026-06-10 10:16 UTCEG score recompute
  31. 2026-06-10 10:16 UTCGHSA enrichment
  32. 2026-06-09 23:01 UTCEG score recompute
  33. 2026-06-09 23:01 UTCGHSA enrichment
  34. 2026-06-09 09:38 UTCEG score recompute
  35. 2026-06-09 09:38 UTCGHSA enrichment
  36. 2026-06-08 22:12 UTCEG score recompute
  37. 2026-06-08 22:12 UTCGHSA enrichment
  38. 2026-06-08 14:17 UTCEPSS rescore
  39. 2026-06-08 14:17 UTCEPSS rescore
  40. 2026-06-08 10:33 UTCEG score recompute
  41. 2026-06-08 10:33 UTCGHSA enrichment
  42. 2026-06-07 23:18 UTCEG score recompute
  43. 2026-06-07 23:18 UTCGHSA enrichment
  44. 2026-06-07 15:25 UTCEPSS rescore
  45. 2026-06-07 15:25 UTCEPSS rescore
  46. 2026-06-07 12:03 UTCEG score recompute
  47. 2026-06-07 12:03 UTCGHSA enrichment
  48. 2026-06-07 00:48 UTCEG score recompute
  49. 2026-06-07 00:48 UTCGHSA enrichment
  50. 2026-06-06 13:47 UTCEPSS rescore
  51. 2026-06-06 13:47 UTCEPSS rescore
  52. 2026-06-06 13:32 UTCEG score recompute
  53. 2026-06-06 13:32 UTCGHSA enrichment
  54. 2026-06-06 02:17 UTCEG score recompute
  55. 2026-06-06 02:17 UTCGHSA enrichment
  56. 2026-06-06 02:17 UTCEG score recompute
  57. 2026-06-06 02:17 UTCGHSA enrichment
  58. 2026-06-05 22:47 UTCEPSS rescore
  59. 2026-06-05 14:58 UTCEG score recompute
  60. 2026-06-05 14:58 UTCGHSA enrichment
  61. 2026-06-05 06:10 UTCEPSS rescore
  62. 2026-06-05 06:10 UTCEPSS rescore
  63. 2026-06-05 03:43 UTCEG score recompute
  64. 2026-06-05 03:43 UTCGHSA enrichment
  65. 2026-06-04 16:26 UTCEG score recompute
  66. 2026-06-04 16:26 UTCGHSA enrichment
  67. 2026-06-04 13:12 UTCEPSS rescore
  68. 2026-06-04 13:12 UTCEPSS rescore
  69. 2026-06-04 05:11 UTCEG score recompute
  70. 2026-06-04 05:11 UTCGHSA enrichment
  71. 2026-06-03 17:55 UTCEG score recompute
  72. 2026-06-03 17:55 UTCGHSA enrichment
  73. 2026-06-03 06:40 UTCEG score recompute
  74. 2026-06-03 06:40 UTCGHSA enrichment
  75. 2026-06-02 20:13 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 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.