serial: core: fix infinite loop in handle_tx() for PORT_UNKNOWN
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 455ce986fa356ff43a43c0d363ba95fa152f21d5| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
serial: core: fix infinite loop in handle_tx() for PORT_UNKNOWN
uart_write_room() and uart_write() behave inconsistently when xmit_buf is NULL (which happens for PORT_UNKNOWN ports that were never properly initialized):
- uart_write_room() returns kfifo_avail() which can be > 0 - uart_write() checks xmit_buf and returns 0 if NULL
This inconsistency causes an infinite loop in drivers that rely on tty_write_room() to determine if they can write:
while (tty_write_room(tty) > 0) { written = tty->ops->write(...); // written is always 0, loop never exits }
For example, caif_serial's handle_tx() enters an infinite loop when used with PORT_UNKNOWN serial ports, causing system hangs.
Fix by making uart_write_room() also check xmit_buf and return 0 if it's NULL, consistent with uart_write().
From the CVE record · Linux
In the Linux kernel serial core, an uninitialized PORT_UNKNOWN port can report writable space even though writes return zero. This can trap drivers such as caif_serial in an infinite loop and hang the system. The input does not specify how the condition can be triggered or whether authentication or user interaction is required.
Engineers running Linux kernels with serial drivers should check their kernel versions against the vendor advisory; affected versions are not specified.