usb: core: clear both ep_in and ep_out for non-ep0 control endpoints

Summary

In the Linux kernel, the following vulnerability has been resolved: usb: core: clear both ep_in and ep_out for non-ep0 control endpoints In usb_enable_endpoint(), non-zero control endpoints (where usb_endpoint_xfer_control(&ep->desc) is true) populate both dev->ep_in[epnum] and dev->ep_out[epnum] with the same struct usb_host_endpoint pointer. However, usb_disable_endpoint() only clears either dev->ep_out[epnum] or dev->ep_in[epnum] depending on the direction bit of epaddr when reset_hardware is set, leaving the opposite direction's array slot pointing to the disabled/freed endpoint. Clear both dev->ep_out[epnum] and dev->ep_in[epnum] when disabling a non-ep0 control endpoint with reset_hardware set, and update the function kerneldoc accordingly. Tested in QEMU against Linux 7.3.0-rc3 using dummy_hcd and raw-gadget to enumerate a USB device with a non-zero control endpoint (bEndpointAddress 0x01, bmAttributes USB_ENDPOINT_XFER_CONTROL), verifying that both dev->ep_in[1] and dev->ep_out[1] are cleared when the interface is disabled.

Timeline

1. Oct 18, 2026, 3:47 PM UTCCVE published
2. Oct 21, 2026, 12:56 PM UTCRecord last updated

Affected versions

• Linux Linux

  From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 198d74dcfa129523125f46a89479d3b446b17dbe; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 7a9f61476b0e8002092a52ee8295edeeb0a28d1e; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 1da16c46b8d7101b74bc2d72a04e23cf5c7ddea1; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in c50413ecb662ea43c7f487632c8114721743a277; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 0e8baa78d872f2db440d8b9ded946ab8dceb89eb

• Linux Linux

  2.6.12

• KernelLinux

  From 2.6.12 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.113; From 6.13.0 · fixed in 6.18.56; From 6.19.0 · fixed in 7.2.10

References 5