CVE-2026-58093

The TIOCSCTTY ioctl handler drops the tty lock in order to acquire the process tree lock. After reacquiring the tty lock, the handler did not revalidate the state of the terminal, and could proceed to link a terminal that was concurrently being destroyed to the calling process' session. An...

EUVD-2026-66250

The TIOCSCTTY ioctl handler drops the tty lock in order to acquire the process tree lock. After reacquiring the tty lock, the handler did not revalidate the state of the terminal, and could proceed to link a terminal that was concurrently being destroyed to the calling process' session. An...

CVE-2026-58093: Concurrent Execution using Shared Resource with Improper Synchronization

The TIOCSCTTY ioctl handler drops the tty lock in order to acquire the process tree lock. After reacquiring the tty lock, the handler did not revalidate the state of the terminal, and could proceed to link a terminal that was concurrently being destroyed to the calling process' session. An...

PT-2026-81936

Name of the Vulnerable Software and Affected Versions The product name cannot be determined affected versions not specified Description A race condition exists in the TIOCSCTTY ioctl handler. The handler releases the tty lock to acquire the process tree lock but fails to revalidate the terminal...

CVE-2022-49441 tty: fix deadlock caused by calling printk() under tty_port->lock

In the Linux kernel, the following vulnerability has been resolved: tty: fix deadlock caused by calling printk under ttyport-lock ptywrite invokes kmalloc which may invoke a normal printk to print failure message. This can cause a deadlock in the scenario reported by syz-bot below: CPU0 CPU1 CPU2...