<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 01 Oct 2026 19:56:30 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21820 — tty: xilinx_uartps: split sysrq handling</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-21820</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tty: xilinx_uartps: split sysrq handling&lt;/p&gt;
&lt;p&gt;lockdep detects the following circular locking dependency:&lt;/p&gt;
&lt;p&gt;CPU 0                      CPU 1
========================== ============================
cdns_uart_isr()            printk()
  uart_port_lock(port)       console_lock()
			     cdns_uart_console_write()
                               if (!port-&amp;gt;sysrq)
                                 uart_port_lock(port)
  uart_handle_break()
    port-&amp;gt;sysrq = ...
  uart_handle_sysrq_char()
    printk()
      console_lock()&lt;/p&gt;
&lt;p&gt;The fixed commit attempts to avoid this situation by only taking the
port lock in cdns_uart_console_write if port-&amp;gt;sysrq unset. However, if
(as shown above) cdns_uart_console_write runs before port-&amp;gt;sysrq is set,
then it will try to take the port lock anyway. This may result in a
deadlock.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tty: xilinx_uartps: split sysrq handling&lt;/p&gt;
&lt;p&gt;lockdep detects the following circular locking dependency:&lt;/p&gt;
&lt;p&gt;CPU 0                      CPU 1
========================== ============================
cdns_uart_isr()            printk()
  uart_port_lock(port)       console_lock()
			     cdns_uart_console_write()
                               if (!port-&amp;gt;sysrq)
                                 uart_port_lock(port)
  uart_handle_break()
    port-&amp;gt;sysrq = ...
  uart_handle_sysrq_char()
    printk()
      console_lock()&lt;/p&gt;
&lt;p&gt;The fixed commit attempts to avoid this situation by only taking the
port lock in cdns_uart_console_write if port-&amp;gt;sysrq unset. However, if
(as shown above) cdns_uart_console_write runs before port-&amp;gt;sysrq is set,
then it will try to take the port lock anyway. This may result in a
deadlock.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-21820</guid>
    </item>
  </channel>
</rss>
