<?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://cve.radiocsirt.org</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>Fri, 09 Oct 2026 18:50:11 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-26999 — serial/pmac_zilog: Remove flawed mitigation for rx irq flood</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-26999</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;serial/pmac_zilog: Remove flawed mitigation for rx irq flood&lt;/p&gt;
&lt;p&gt;The mitigation was intended to stop the irq completely. That may be
better than a hard lock-up but it turns out that you get a crash anyway
if you&amp;#39;re using pmac_zilog as a serial console:&lt;/p&gt;
&lt;p&gt;ttyPZ0: pmz: rx irq flood !
BUG: spinlock recursion on CPU#0, swapper/0&lt;/p&gt;
&lt;p&gt;That&amp;#39;s because the pr_err() call in pmz_receive_chars() results in
pmz_console_write() attempting to lock a spinlock already locked in
pmz_interrupt(). With CONFIG_DEBUG_SPINLOCK=y, this produces a fatal
BUG splat. The spinlock in question is the one in struct uart_port.&lt;/p&gt;
&lt;p&gt;Even when it&amp;#39;s not fatal, the serial port rx function ceases to work.
Also, the iteration limit doesn&amp;#39;t play nicely with QEMU, as can be
seen in the bug report linked below.&lt;/p&gt;
&lt;p&gt;A web search for other reports of the error message &amp;#34;pmz: rx irq flood&amp;#34;
didn&amp;#39;t produce anything. So I don&amp;#39;t think this code is needed any more.
Remove it.&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;serial/pmac_zilog: Remove flawed mitigation for rx irq flood&lt;/p&gt;
&lt;p&gt;The mitigation was intended to stop the irq completely. That may be
better than a hard lock-up but it turns out that you get a crash anyway
if you&amp;#39;re using pmac_zilog as a serial console:&lt;/p&gt;
&lt;p&gt;ttyPZ0: pmz: rx irq flood !
BUG: spinlock recursion on CPU#0, swapper/0&lt;/p&gt;
&lt;p&gt;That&amp;#39;s because the pr_err() call in pmz_receive_chars() results in
pmz_console_write() attempting to lock a spinlock already locked in
pmz_interrupt(). With CONFIG_DEBUG_SPINLOCK=y, this produces a fatal
BUG splat. The spinlock in question is the one in struct uart_port.&lt;/p&gt;
&lt;p&gt;Even when it&amp;#39;s not fatal, the serial port rx function ceases to work.
Also, the iteration limit doesn&amp;#39;t play nicely with QEMU, as can be
seen in the bug report linked below.&lt;/p&gt;
&lt;p&gt;A web search for other reports of the error message &amp;#34;pmz: rx irq flood&amp;#34;
didn&amp;#39;t produce anything. So I don&amp;#39;t think this code is needed any more.
Remove it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-26999</guid>
    </item>
  </channel>
</rss>
