USB: serial: digi_acceleport: fix write buffer corruption
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 1243f120790042c2ac92e84e797dacc75fff4366| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
USB: serial: digi_acceleport: fix write buffer corruption
The digi_write_inb_command() is supposed to wait for the write urb to become available or return an error, but instead it updates the transfer buffer and tries to resubmit the urb on timeout.
To make things worse, for commands like break control where no timeout is used, the driver would corrupt the urb immediately due to a broken jiffies comparison (on 32-bit machines this takes five minutes of uptime to trigger due to INITIAL_JIFFIES).
Fix this by adding the missing return on timeout and waiting indefinitely when no timeout has been specified as intended.
This issue was (sort of) flagged by Sashiko when reviewing an unrelated change to the driver.
From the CVE record · Linux
The Linux kernel’s digi_acceleport USB serial driver can corrupt a write transfer buffer when a write request times out. Commands without a timeout can trigger the corruption immediately; on 32-bit machines, the faulty timing comparison can trigger it after five minutes of uptime. The input does not establish an attacker action, access requirement, or user-interaction requirement.
Engineers running Linux systems that use the digi_acceleport USB serial driver should check their kernel versions; affected versions were not provided.