serial: core: fix transmit-buffer reset and memleak
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 00de977f9e0aa9760d9a79d1e41ff780f74e3424, Kernel 011f6c92b5bf6e1fbfdedc8b5232f64c1c493206, Kernel 1179b168fa3f3a6aae3bd140000455a0e58457db and 4 more.
In the Linux kernel, the following vulnerability has been resolved: serial: core: fix transmit-buffer reset and memleak Commit 761ed4a94582 ("tty: serial_core: convert uart_close to use tty_port_close") converted serial core to use tty_port_close() but failed to notice that the transmit buffer still needs to be freed on final close. Not freeing the transmit buffer means that the buffer is no longer cleared on next open so that any ioctl() waiting for the buffer to drain might wait indefinitely (e.g. on termios changes) or that stale data can end up being transmitted in case tx is restarted. Furthermore, the buffer of any port that has been opened would leak on driver unbind. Note that the port lock is held when clearing the buffer pointer due to the ldisc race worked around by commit a5ba1d95e46e ("uart: fix race between uart_put_char() and uart_shutdown()"). Also note that the tty-port shutdown() callback is not called for console ports so it is not strictly necessary to free the buffer page after releasing the lock (cf. d72402145ace ("tty/serial: do not free trasnmit buffer page under port lock")).
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.9, >=761ed4a94582ab291aa24dcbea4e01e8936488c8 <00de977f9e0aa9760d9a79d1e41ff780f74e3424, >=761ed4a94582ab291aa24dcbea4e01e8936488c8 <011f6c92b5bf6e1fbfdedc8b5232f64c1c493206, >=761ed4a94582ab291aa24dcbea4e01e8936488c8 <1179b168fa3f3a6aae3bd140000455a0e58457db, >=761ed4a94582ab291aa24dcbea4e01e8936488c8 <64e491c1634b73d3bddc081d08620bdc92ab2c12, >=761ed4a94582ab291aa24dcbea4e01e8936488c8 <c5da8aa441053958594f94254592bb41264bdfbf, >=761ed4a94582ab291aa24dcbea4e01e8936488c8 <e1722acf4f0d4d67b60f57e08ce16f8b66cd4b8f, >=761ed4a94582ab291aa24dcbea4e01e8936488c8 <e74d9663fd57640fc3394abb5c76fa95b9cc2f2e | 00de977f9e0aa9760d9a79d1e41ff780f74e3424, 011f6c92b5bf6e1fbfdedc8b5232f64c1c493206, 1179b168fa3f3a6aae3bd140000455a0e58457db, 64e491c1634b73d3bddc081d08620bdc92ab2c12, c5da8aa441053958594f94254592bb41264bdfbf, e1722acf4f0d4d67b60f57e08ce16f8b66cd4b8f, e74d9663fd57640fc3394abb5c76fa95b9cc2f2e |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket