CVE-2026-43250

High

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

SeverityHigh
CVSS7.8
Exploit probability—
ProductLinux Kernel
PublishedMay 6, 2026
First seenMay 6, 2026

How to fix

Update
  • linux linux_kernel6.12.75, 6.18.16, 6.19.6 or later

Affected products

ProductAffected versionsFixed in
linux linux_kernel2.6.29 ≤ v < 6.12.75, 6.13 ≤ v < 6.18.16, 6.19 ≤ v < 6.19.66.12.75, 6.18.16, 6.19.6
microsoft azl3_kernel_6.6.137.1-2No range specified—
microsoft azl3_kernel_6.6.138.1-1No range specified—
microsoft azl3_kernel_6.6.141.1-1No range specified—
microsoft azl3_kernel_6.6.143.1-1No range specified—
microsoft azl3_kernel_6.6.144.1-1No range specified—
microsoft azl3_kernel_6.6.145.2-1No range specified—
microsoft azl3_kernel_6.6.157.1-1No range specified—
microsoft azl3_kernel_6.6.139.1-1No range specified—
microsoft azl3_kernel_6.6.150.1-1No range specified—
microsoft azl3_kernel_6.6.152.1-1No range specified—
microsoft azl3_kernel_6.6.159.1-1No range specified—

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.