<?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>Mon, 05 Oct 2026 01:50:43 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64528 — tty: serial: samsung: Remove redundant port lock acquisition in rx helpers</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64528</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: serial: samsung: Remove redundant port lock acquisition in rx helpers&lt;/p&gt;
&lt;p&gt;Sashiko identified a deadlock when the console flow is engaged [1].&lt;/p&gt;
&lt;p&gt;When console flow control is enabled (UPF_CONS_FLOW),
s3c24xx_serial_stop_tx() calls s3c24xx_serial_rx_enable() and
s3c24xx_serial_start_tx() calls s3c24xx_serial_rx_disable().&lt;/p&gt;
&lt;p&gt;The serial core framework invokes the .stop_tx() and .start_tx()
callbacks with the port-&amp;gt;lock spinlock already held. Furthermore, all
internal driver paths that invoke stop_tx (such as the DMA TX
completion handler s3c24xx_serial_tx_dma_complete() or the PIO TX IRQ
handler s3c24xx_serial_tx_irq()) also acquire port-&amp;gt;lock prior to
calling it. (Note that s3c24xx_serial_start_tx() is only invoked by the
serial core).&lt;/p&gt;
&lt;p&gt;However, s3c24xx_serial_rx_enable() and s3c24xx_serial_rx_disable()
unconditionally attempt to acquire port-&amp;gt;lock again using
uart_port_lock_irqsave(). Since spinlocks are not recursive, this
causes a deadlock on the same CPU when console flow control is engaged.&lt;/p&gt;
&lt;p&gt;Remove the redundant lock acquisition from both rx helper functions.&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: serial: samsung: Remove redundant port lock acquisition in rx helpers&lt;/p&gt;
&lt;p&gt;Sashiko identified a deadlock when the console flow is engaged [1].&lt;/p&gt;
&lt;p&gt;When console flow control is enabled (UPF_CONS_FLOW),
s3c24xx_serial_stop_tx() calls s3c24xx_serial_rx_enable() and
s3c24xx_serial_start_tx() calls s3c24xx_serial_rx_disable().&lt;/p&gt;
&lt;p&gt;The serial core framework invokes the .stop_tx() and .start_tx()
callbacks with the port-&amp;gt;lock spinlock already held. Furthermore, all
internal driver paths that invoke stop_tx (such as the DMA TX
completion handler s3c24xx_serial_tx_dma_complete() or the PIO TX IRQ
handler s3c24xx_serial_tx_irq()) also acquire port-&amp;gt;lock prior to
calling it. (Note that s3c24xx_serial_start_tx() is only invoked by the
serial core).&lt;/p&gt;
&lt;p&gt;However, s3c24xx_serial_rx_enable() and s3c24xx_serial_rx_disable()
unconditionally attempt to acquire port-&amp;gt;lock again using
uart_port_lock_irqsave(). Since spinlocks are not recursive, this
causes a deadlock on the same CPU when console flow control is engaged.&lt;/p&gt;
&lt;p&gt;Remove the redundant lock acquisition from both rx helper functions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64528</guid>
    </item>
  </channel>
</rss>
