Vulnerabilities · 2025 · Linux
CVE-2025-21820
Linux Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: tty: xilinx_uartps: split sysrq handling lockdep detects the following circular locking dependency: CPU 0 CPU 1 ========================== ============================ cdns_uart_isr() printk() uart_port_lock(port) console_lock() cdns_uart_console_write() if (!port->sysrq) uart_port_lock(port) uart_handle_break() port->sysrq = ... uart_handle_sysrq_char() printk() console_lock() The fixed commit attempts to avoid this situation by only taking the port lock in cdns_uart_console_write if port->sysrq unset. However, if (as shown above) cdns_uart_console_write runs before port->sysrq is set, then it will try to take the port lock anyway. This may result in a deadlock. Fix this by splitting sysrq handling into two parts. We use the prepare helper under the port lock and defer handling until we release the lock.
Affected products
Linux Kernel. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Linux Kernel runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/4410dba9807a17a93f649a9f5870ceaf30a675a3 · Patch
- git.kernel.org/stable/c/8ea0e7b3d7b8f2f0fc9db491ff22a0abe120801c · Patch
- git.kernel.org/stable/c/9b88a7c4584ba67267a051069b8abe44fc9595b2 · Patch
- git.kernel.org/stable/c/b06f388994500297bb91be60ffaf6825ecfd2afe · Patch
- git.kernel.org/stable/c/de5bd24197bd9ee37ec1e379a3d882bbd15c5065 · Patch
- git.kernel.org/stable/c/e22a97700901ba5e8bf8db68056a0d50f9440cae
- lists.debian.org/debian-lts-announce/2025/03/msg00028.html
- nvd.nist.gov/vuln/detail/CVE-2025-21820
- cve.org/CVERecord?id=CVE-2025-21820
More vulnerabilities in Linux products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.