CVE-2025-21820
Last modified
CVE-2025-21820 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 4.6, < 6.1.129 |
| Linux | Linux Kernel | >= 6.2, < 6.6.78 |
| Linux | Linux Kernel | >= 6.7, < 6.12.14 |
| Linux | Linux Kernel | >= 6.13, < 6.13.3 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-21820?
How severe is CVE-2025-21820?
How do I fix CVE-2025-21820?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-21815In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-21816In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21817In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21818Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2025-21819In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-2182A problem with the implementation of the MACsec protocol in …5.6
- CVE-2025-21821In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21822In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21823In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21824In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21825In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2025-21826In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2025-21820?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
