<?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>Wed, 30 Sep 2026 16:42:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-63798 — irqchip/imgpdc: Fix resource leak, add missing chained handler cleanup on remove</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-63798</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;irqchip/imgpdc: Fix resource leak, add missing chained handler cleanup on remove&lt;/p&gt;
&lt;p&gt;The driver allocates domain generic chips using
irq_alloc_domain_generic_chips() during probe and sets up chained
handlers using irq_set_chained_handler_and_data(). However, on driver
removal, the generic chips are not freed and the chained handlers are
not removed.&lt;/p&gt;
&lt;p&gt;The generic chips remain on the global gc_list and may later be accessed by
generic interrupt chip suspend, resume, or shutdown callbacks after the
driver has been removed, potentially resulting in a use-after-free and
kernel crash.&lt;/p&gt;
&lt;p&gt;The chained handlers that were installed in probe for peripheral and
syswake interrupts are also left dangling, which can lead to spurious
interrupts accessing freed memory.&lt;/p&gt;
&lt;p&gt;Fix these issues by:&lt;/p&gt;
&lt;p&gt;- Setting IRQ_DOMAIN_FLAG_DESTROY_GC flag in domain-&amp;gt;flags, so the
    core code automatically removes generic chips when irq_domain_remove()
    is called&lt;/p&gt;
&lt;p&gt;- Clearing all chained handlers with NULL in pdc_intc_remove()&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;irqchip/imgpdc: Fix resource leak, add missing chained handler cleanup on remove&lt;/p&gt;
&lt;p&gt;The driver allocates domain generic chips using
irq_alloc_domain_generic_chips() during probe and sets up chained
handlers using irq_set_chained_handler_and_data(). However, on driver
removal, the generic chips are not freed and the chained handlers are
not removed.&lt;/p&gt;
&lt;p&gt;The generic chips remain on the global gc_list and may later be accessed by
generic interrupt chip suspend, resume, or shutdown callbacks after the
driver has been removed, potentially resulting in a use-after-free and
kernel crash.&lt;/p&gt;
&lt;p&gt;The chained handlers that were installed in probe for peripheral and
syswake interrupts are also left dangling, which can lead to spurious
interrupts accessing freed memory.&lt;/p&gt;
&lt;p&gt;Fix these issues by:&lt;/p&gt;
&lt;p&gt;- Setting IRQ_DOMAIN_FLAG_DESTROY_GC flag in domain-&amp;gt;flags, so the
    core code automatically removes generic chips when irq_domain_remove()
    is called&lt;/p&gt;
&lt;p&gt;- Clearing all chained handlers with NULL in pdc_intc_remove()&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-63798</guid>
    </item>
  </channel>
</rss>
