USB: serial: cypress_m8: validate interrupt packet headers
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3416eaa1f8f8d516b77de514e14cf8da256d28fb · < ae03453f2c809ca3cf73753269fa6184dea7160f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
USB: serial: cypress_m8: validate interrupt packet headers
cypress_read_int_callback() parses the interrupt-in buffer according to the selected Cypress packet format. Format 1 has a two-byte status/count header and format 2 has a one-byte combined status/count header. The usb-serial core sizes the interrupt-in buffer from the endpoint descriptor's wMaxPacketSize, and successful interrupt transfers can complete short when URB_SHORT_NOT_OK is not set.
Check that the completed packet contains the selected header before reading it. Malformed short reports are ignored and the interrupt URB is resubmitted through the existing retry path, preventing out-of-bounds header-byte reads.
KASAN report as below: KASAN slab-out-of-bounds in cypress_read_int_callback+0x240/0x7f0 Read of size 1 Call trace: cypress_read_int_callback() (drivers/usb/serial/cypress_m8.c:1009) __usb_hcd_giveback_urb() dummy_timer()
[ johan: use constants in header length sanity checks ]
From the CVE record · Linux
The Linux kernel’s cypress_m8 USB serial driver can read beyond an interrupt buffer when a completed packet is shorter than the selected format’s header. A malformed short USB interrupt report can trigger this read; the input does not specify an authentication requirement or user interaction.
Engineers running Linux kernels with the Cypress USB serial driver should check their kernel’s status; affected versions are not specified.