12 matches found
CVE-2026-98753
In the Linux kernel, the following vulnerability has been resolved: tty: ttyport: restore TTYIOERROR on activation failure Make sure to restore the TTYIOERROR flag if activation fails to prevent I/O attempts on a port that is gone or powered down. This specifically avoids issues like kernel panic...
EUVD-2026-103838
In the Linux kernel, the following vulnerability has been resolved: tty: ttyport: restore TTYIOERROR on activation failure Make sure to restore the TTYIOERROR flag if activation fails to prevent I/O attempts on a port that is gone or powered down. This specifically avoids issues like kernel panic...
CVE-2026-98753
The Linux kernel contains a vulnerability in the tty_port component where the TTY_IO_ERROR flag is not restored upon activation failure. This oversight creates a race condition during tty ioctl , hangup, and open operations. If activation fails, the lack of this flag can lead to I/O attempts on p...
CVE-2026-98753 tty: tty_port: restore TTY_IO_ERROR on activation failure
In the Linux kernel, the following vulnerability has been resolved: tty: ttyport: restore TTYIOERROR on activation failure Make sure to restore the TTYIOERROR flag if activation fails to prevent I/O attempts on a port that is gone or powered down. This specifically avoids issues like kernel panic...
CVE-2026-98753
In the Linux kernel, the following vulnerability has been resolved: tty: ttyport: restore TTYIOERROR on activation failure Make sure to restore the TTYIOERROR flag if activation fails to prevent I/O attempts on a port that is gone or powered down. This specifically avoids issues like kernel panic...
EUVD-2022-54788
Malicious code in bioql PyPI...
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...
CVE-2022-49441
CVE-2022-49441 relates to a Linux kernel deadlock in tty handling. The root cause is a potential deadlock when kmalloc() path could trigger a printk() while holding tty_port->lock, enabling a cycle with console ownership locks. The described failing scenario involves multiple CPUs acquiring po...
CVE-2022-49441: Improper Locking
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...
GSD-2022-1003887 tty: fix deadlock caused by calling printk() under tty_port->lock
tty: fix deadlock caused by calling printk under ttyport-lock This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven. This ID is fixed in Linux Kernel version v4.19.247 by commit...
GSD-2022-1003334 tty: fix deadlock caused by calling printk() under tty_port->lock
tty: fix deadlock caused by calling printk under ttyport-lock This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven. This ID is fixed in Linux Kernel version v5.15.46 by commit...
GSD-2022-1002709 tty: fix deadlock caused by calling printk() under tty_port->lock
tty: fix deadlock caused by calling printk under ttyport-lock This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven. This ID is fixed in Linux Kernel version v5.18.3 by commit...