{"uuid": "1ec2330f-9648-4973-bd53-7c0a50eec740", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21820", "type": "seen", "source": "https://t.me/cvedetector/19082", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21820 - Xilinx tty UART Lock Deadlock Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21820 \nPublished : Feb. 27, 2025, 8:16 p.m. | 1\u00a0hour, 21\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ntty: xilinx_uartps: split sysrq handling  \n  \nlockdep detects the following circular locking dependency:  \n  \nCPU 0                      CPU 1  \n========================== ============================  \ncdns_uart_isr()            printk()  \n  uart_port_lock(port)       console_lock()  \n        cdns_uart_console_write()  \n                               if (!port->sysrq)  \n                                 uart_port_lock(port)  \n  uart_handle_break()  \n    port->sysrq = ...  \n  uart_handle_sysrq_char()  \n    printk()  \n      console_lock()  \n  \nThe fixed commit attempts to avoid this situation by only taking the  \nport lock in cdns_uart_console_write if port->sysrq unset. However, if  \n(as shown above) cdns_uart_console_write runs before port->sysrq is set,  \nthen it will try to take the port lock anyway. This may result in a  \ndeadlock.  \n  \nFix this by splitting sysrq handling into two parts. We use the prepare  \nhelper under the port lock and defer handling until we release the lock. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-27T23:26:58.000000Z"}