CVE-2026-43250

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

State
Published
Severity
Not scored
Published
May 6, 2026
Updated
Oct 30, 2026
Reserved
May 1, 2026

Read the record on cve.org

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

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • aa69a8093ff985873cb44fe1157bd6db29a20fe4 to before 1497998749600411d75e60a44f7e572b2348bd9aAffected
  • aa69a8093ff985873cb44fe1157bd6db29a20fe4 to before aad97c92119cb85db105ddda4a44c86cc0748e8cAffected
  • aa69a8093ff985873cb44fe1157bd6db29a20fe4 to before 1b72b834511d17f4d069d512f78671f3f210a2f1Affected
  • aa69a8093ff985873cb44fe1157bd6db29a20fe4 to before f4fbf2d4750d12ac8525d2efac1016fa0d84d4ecAffected
  • aa69a8093ff985873cb44fe1157bd6db29a20fe4 to before e74c436f8568af1c60942469d0a2300b3ada3857Affected
  • aa69a8093ff985873cb44fe1157bd6db29a20fe4 to before cea2a1257a3b5ea3e769a445b34af13e6aa5a123Affected
LinuxLinux
  • 2.6.29Affected
  • before 2.6.29Not affected
  • 6.1.191 through 6.1.*Not affected
  • 6.6.160 through 6.6.*Not affected
  • 6.12.75 through 6.12.*Not affected
  • 6.18.16 through 6.18.*Not affected
  • 6.19.6 through 6.19.*Not affected
  • 7.0 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.