usb: cdc-acm: Check control transfer buffer size before access
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < f64079bef6a8a7823358c3f352ea29a617844636| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
usb: cdc-acm: Check control transfer buffer size before access
If the first fragment is shorter than struct usb_cdc_notification, we can't calculate an expected_size. Log an error and discard the notification instead of reading lengths from memory outside the received data, which can lead to memory corruption when the expected_size decreases between fragments, causing `expected_size - acm->nb_index` to wrap.
This issue has been present since the beginning of git history; however, it only leads to memory corruption since commit ea2583529cd1 ("cdc-acm: reassemble fragmented notifications").
A mitigating factor is that acm_ctrl_irq() can only execute after userspace has opened /dev/ttyACM*; but if ModemManager is running, ModemManager will do that automatically depending on the USB device's vendor/product IDs and its other interfaces.
From the CVE record · Linux
The Linux kernel’s USB cdc-acm driver can read beyond a short notification fragment, potentially causing memory corruption. This can occur after userspace opens /dev/ttyACM*; ModemManager may open it automatically for some USB devices. The issue has been present since the beginning of git history but can cause memory corruption only since commit ea2583529cd1.
Engineers running Linux kernels containing commit ea2583529cd1 should check their systems.