Deadlock Vulnerability in Linux Kernel tty
Summary
GSD-2022-1003334: tty: fix deadlock caused by calling printk() under tty_port->lock. Affects Kernel versions >= b6da31b2c07c46f2dcad1d86caa835227a16d9ff, < 18ca0d55e8639b911df8aae1b47598b13f9acded. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The Linux Kernel is the core component of the Linux operating system, responsible for managing system resources and providing an interface for applications to interact with the hardware. The tty subsystem in the Linux Kernel handles terminal input and output, allowing users to interact with the system through text-based interfaces. The tty subsystem includes the tty driver, which manages the communication between the terminal device and the kernel. The vulnerability identified in this report affects the tty subsystem in the Linux Kernel.
Vulnerability Detail
The vulnerability in the Linux Kernel tty subsystem arises from a deadlock caused by calling printk() under tty_port->lock. This can lead to a situation where a process holding the tty_port->lock attempts to acquire the printk lock, resulting in a deadlock. An attacker could potentially exploit this vulnerability to cause a denial-of-service (DoS) condition by triggering the deadlock. The vulnerability was introduced in version v4.18 of the Linux Kernel and is fixed in version v5.15.46.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability.
Conclusion
The vulnerability in the Linux Kernel tty subsystem can lead to a deadlock situation, potentially causing a denial-of-service (DoS) condition. It is recommended to update the Linux Kernel to version v5.15.46 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can be exploited to cause a denial-of-service (DoS) condition by triggering a deadlock in the tty subsystem of the Linux Kernel.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and Vulert will analyze it for any open-source vulnerabilities, including this one.
Yes, the vulnerability is fixed in Linux Kernel version v5.15.46. It is recommended to update to this version or a later one to mitigate the vulnerability.
No, this vulnerability requires local access to the system in order to trigger the deadlock in the tty subsystem.
There are no known instances of this vulnerability being exploited in the wild.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
