usb: cdc-acm: Check control transfer buffer size before access
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.4.291, 5.10.235, 5.15.179, 6.1.129, 6.6.79, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in a4e1ae5c0533964170197e4fb4f33bc8c1db5cd2; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 90dd2f1b7342b9a671a5ea4160f408037b92b118; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 871619c2b78fdfe05afb4e8ba548678687beb812; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 7828e9363ac4d23b02419bf2a45b9f1d9fb35646; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 6abb510251e75f875797d8983a830e6731fa281c; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in f64079bef6a8a7823358c3f352ea29a617844636; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 383d516a0ebc8641372b521c8cb717f0f1834831; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in e563b01208f4d1f609bcab13333b6c0e24ce6a01
- Linux Linux
2.6.12
- KernelLinux
From 2.6.12 · fixed in 5.4.291; From 5.5.0 · fixed in 5.10.235; From 5.11.0 · fixed in 5.15.179; From 5.16.0 · fixed in 6.1.129; From 6.2.0 · fixed in 6.6.79; From 6.7.0 · fixed in 6.12.16; From 6.13.0 · fixed in 6.13.4
References 9
git.kernel.org
- stable/c/a4e1ae5c0533964170197e4fb4f33bc8c1db5cd2
- stable/c/90dd2f1b7342b9a671a5ea4160f408037b92b118
- stable/c/871619c2b78fdfe05afb4e8ba548678687beb812
- stable/c/7828e9363ac4d23b02419bf2a45b9f1d9fb35646
- stable/c/6abb510251e75f875797d8983a830e6731fa281c
- stable/c/f64079bef6a8a7823358c3f352ea29a617844636
- stable/c/383d516a0ebc8641372b521c8cb717f0f1834831
- stable/c/e563b01208f4d1f609bcab13333b6c0e24ce6a01