serial: max3100: Lock port->lock when calling uart_handle_cts_change()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 7831d56b0a3544cbb6f82f76c34ca95e24d5b676 · < 93df2fba6c7dfa9a2f08546ea9a5ca4728758458| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
serial: max3100: Lock port->lock when calling uart_handle_cts_change()
uart_handle_cts_change() has to be called with port lock taken, Since we run it in a separate work, the lock may not be taken at the time of running. Make sure that it's taken by explicitly doing that. Without it we got a splat:
WARNING: CPU: 0 PID: 10 at drivers/tty/serial/serial_core.c:3491 uart_handle_cts_change+0xa6/0xb0 ... Workqueue: max3100-0 max3100_work [max3100] RIP: 0010:uart_handle_cts_change+0xa6/0xb0 ... max3100_handlerx+0xc5/0x110 [max3100] max3100_work+0x12a/0x340 [max3100]
From the CVE record · Linux
The Linux kernel's max3100 serial driver can call uart_handle_cts_change() without holding the required port lock, producing a kernel warning. The input does not establish whether an attacker can trigger this issue or specify access or user-interaction requirements.
Engineers running Linux kernels with the max3100 serial driver should check their deployments; affected versions are not specified.