<?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>Tue, 29 Sep 2026 10:37:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-97481 — serial: 8250: fix possible ISR soft lockup</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-97481</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: 8250: fix possible ISR soft lockup&lt;/p&gt;
&lt;p&gt;There are rare cases in which the host gets stuck in the ISR because it
is flooded with messages during the startup phase.&lt;/p&gt;
&lt;p&gt;The reason for the soft lockup in the ISR is the missing FIFO error IRQ
(FIFOE) handling. Not handling it and reporting IRQ_HANDLED triggers
the IRQ immediately again.&lt;/p&gt;
&lt;p&gt;Fix this by adding a check for the FIFOE status and clearing the FIFO
if no data is ready (DR).&lt;/p&gt;
&lt;p&gt;This behavior was observed on an AM62L device which uses the OMAP 8250
driver. Fix it for all 8250 drivers, since the OMAP driver&amp;#39;s special
IRQ setup handling may trigger this behavior more frequently, but it
is not ensured that other 8250 drivers aren&amp;#39;t affected.&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: 8250: fix possible ISR soft lockup&lt;/p&gt;
&lt;p&gt;There are rare cases in which the host gets stuck in the ISR because it
is flooded with messages during the startup phase.&lt;/p&gt;
&lt;p&gt;The reason for the soft lockup in the ISR is the missing FIFO error IRQ
(FIFOE) handling. Not handling it and reporting IRQ_HANDLED triggers
the IRQ immediately again.&lt;/p&gt;
&lt;p&gt;Fix this by adding a check for the FIFOE status and clearing the FIFO
if no data is ready (DR).&lt;/p&gt;
&lt;p&gt;This behavior was observed on an AM62L device which uses the OMAP 8250
driver. Fix it for all 8250 drivers, since the OMAP driver&amp;#39;s special
IRQ setup handling may trigger this behavior more frequently, but it
is not ensured that other 8250 drivers aren&amp;#39;t affected.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-97481</guid>
    </item>
  </channel>
</rss>
