tty: port: fix tty_port_tty_vhangup() race
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 7ca0ff9ab3218ec443a7a9ad247e4650373ed41e · < 6b7be3b9b857947e9c1338d4919d4ebd3b75e907| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tty: port: fix tty_port_tty_vhangup() race
Drivers rely on tty_port_tty_vhangup() to synchronously hang up their ports before tearing down resources as part of deregistration (e.g. on physical disconnect).
If tty_port_tty_vhangup() races with another hangup it may however return before the port has been shut down. This is in turn can lead to use-after-free and NULL-pointer dereferences in racing ioctls (including a synchronous hangup) and in processing of racing asynchronous hangups (carrier loss).
Add the missing serialisation to tty_port_tty_vhangup() and tty_port_hangup() so that the former does not return until the port has been shut down also when there is a racing hangup.
Note that serial core does not use tty_port_hangup(), but it already holds the port mutex when clearing port->tty and shutting down the port in uart_hangup().
From the CVE record · Linux
A race in tty_port_tty_vhangup() can let port deregistration proceed before shutdown completes. Concurrent hangups and ioctls can then trigger use-after-free or NULL-pointer dereferences. The input does not specify an attacker's access requirements.
Engineers running the Linux kernel should check their builds; affected versions are not specified.