<?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 07:18:40 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-63798</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-63798</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-63798</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0957 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://vulnerability.circl.lu/vuln/certfr-2026-avi-0957</link>
      <description>certfr-2026-avi-0957</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/certfr-2026-avi-0957</guid>
    </item>
    <item>
      <title>fkie_cve-2026-63798</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-63798</link>
      <description>&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;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/fkie_cve-2026-63798</guid>
    </item>
    <item>
      <title>GHSA-2332-q5fp-53mf</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-2332-q5fp-53mf</link>
      <description>&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;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/ghsa-2332-q5fp-53mf</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-63798 — irqchip/imgpdc: Fix resource leak, add missing chained handler cleanup on remove</title>
      <link>https://vulnerability.circl.lu/vuln/msrc_cve-2026-63798</link>
      <description>msrc_CVE-2026-63798</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/msrc_cve-2026-63798</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11339-1 — kernel-devel-7.1.4-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11339-1</link>
      <description>&lt;p&gt;kernel-devel-7.1.4-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.1.4-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11339-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-63798</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-63798</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: irqchip/imgpdc: Fix resource leak, add missing chained handler cleanup on remove 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. 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. 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. Fix these issues by:   - 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   - 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; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: irqchip/imgpdc: Fix resource leak, add missing chained handler cleanup on remove 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. 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. 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. Fix these issues by:   - 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   - Clearing all chained handlers with NULL in pdc_intc_remove()&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-63798</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2403 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2403</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2403</guid>
    </item>
  </channel>
</rss>
