CVE-2026-43250 Details
Description
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).
A vulnerability in the ChipIdea USB Device Controller (UDC) driver of the Linux kernel can lead to "not page aligned scatter-gather buffer" errors. This issue arises when a USB device is reconnected after being disconnected during an active transfer. The problem occurs because the endpoint nuke function returns requests to the gadget layer without properly unmapping Direct Memory Access (DMA) buffers or cleaning up scatter-gather bounce buffers. When a disconnection happens during a multi-segment DMA transfer, the request's scatter-gather fields retain stale values. If the gadget driver reuses the request on reconnection without reinitializing it, the outdated DMA state can cause the hardware enqueue function to skip necessary DMA mappings and attempt to use invalid DMA addresses, potentially leading to memory corruption.
The vulnerability has been addressed by adding proper DMA unmapping and scatter-gather buffer cleanup in the endpoint nuke function. Users should apply the latest patches from the Linux kernel stable tree to mitigate this issue.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/1b72b834511d17f4d069d512f78671f3f210a2f1 | kernel.org | Patch |
| https://git.kernel.org/stable/c/cea2a1257a3b5ea3e769a445b34af13e6aa5a123 | kernel.org | Patch |
| https://git.kernel.org/stable/c/e74c436f8568af1c60942469d0a2300b3ada3857 | kernel.org | Patch |
| https://git.kernel.org/stable/c/f4fbf2d4750d12ac8525d2efac1016fa0d84d4ec | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-787 | Out-of-bounds Write | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 2.6.29, < 6.12.75 >= 6.13, < 6.18.16 >= 6.19, < 6.19.6 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| May 12, 2026 | Initial Analysis | [email protected] |
| May 6, 2026 | New CVE Received | kernel.org |