<?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 20:41:31 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-37815 — misc: microchip: pci1xxxx: Fix Kernel panic during IRQ handler registration</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-37815</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;misc: microchip: pci1xxxx: Fix Kernel panic during IRQ handler registration&lt;/p&gt;
&lt;p&gt;Resolve kernel panic while accessing IRQ handler associated with the
generated IRQ. This is done by acquiring the spinlock and storing the
current interrupt state before handling the interrupt request using
generic_handle_irq.&lt;/p&gt;
&lt;p&gt;A previous fix patch was submitted where &amp;#39;generic_handle_irq&amp;#39; was
replaced with &amp;#39;handle_nested_irq&amp;#39;. However, this change also causes
the kernel panic where after determining which GPIO triggered the
interrupt and attempting to call handle_nested_irq with the mapped
IRQ number, leads to a failure in locating the registered handler.&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;misc: microchip: pci1xxxx: Fix Kernel panic during IRQ handler registration&lt;/p&gt;
&lt;p&gt;Resolve kernel panic while accessing IRQ handler associated with the
generated IRQ. This is done by acquiring the spinlock and storing the
current interrupt state before handling the interrupt request using
generic_handle_irq.&lt;/p&gt;
&lt;p&gt;A previous fix patch was submitted where &amp;#39;generic_handle_irq&amp;#39; was
replaced with &amp;#39;handle_nested_irq&amp;#39;. However, this change also causes
the kernel panic where after determining which GPIO triggered the
interrupt and attempting to call handle_nested_irq with the mapped
IRQ number, leads to a failure in locating the registered handler.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-37815</guid>
    </item>
  </channel>
</rss>
