tty: abort break signalling on hangup
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f34d7a5b7010b82fe97da95496b9971435530062 · < 94af6cd832e9b4ce39a8fb59144a8f09ab56fd35| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tty: abort break signalling on hangup
The break ioctls can race with hangup and end up calling into a tty driver for a device that is already gone or powered down.
Drivers must handle this race, but TCSBRK and TCSBRKP should still be aborted to avoid calling back into the driver after a user-controlled timeout (possibly even after the tty has been reopened).
Note that drivers should disable any break state on shutdown so just return on hangup (calling break_ctl() again is racy and will most likely fail for drivers handling the race).
From the CVE record · Linux
In the Linux kernel, TCSBRK and TCSBRKP break ioctls can race with a tty hangup. A local user issuing these ioctls may cause a call into the driver after the device is gone or powered down, potentially after a user-controlled timeout. No authentication requirement beyond access to the tty is specified.
Anyone running the Linux kernel should check whether their kernel includes the tty hangup fix; affected versions are not specified.