<?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>Sat, 03 Oct 2026 08:09:27 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-15113</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-15113</link>
      <description>bdu:2025-15113</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-15113</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-22128</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-22128</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-22128</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0449 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0449</link>
      <description>certfr-2025-avi-0449</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0449</guid>
    </item>
    <item>
      <title>EUVD-2026-314194</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314194</link>
      <description>EUVD-2026-314194</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314194</guid>
    </item>
    <item>
      <title>fkie_cve-2025-22128</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-22128</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: ath12k: Clear affinity hint before calling ath12k_pci_free_irq() in error path&lt;/p&gt;
&lt;p&gt;If a shared IRQ is used by the driver due to platform limitation, then the
IRQ affinity hint is set right after the allocation of IRQ vectors in
ath12k_pci_msi_alloc(). This does no harm unless one of the functions
requesting the IRQ fails and attempt to free the IRQ.&lt;/p&gt;
&lt;p&gt;This may end up with a warning from the IRQ core that is expecting the
affinity hint to be cleared before freeing the IRQ:&lt;/p&gt;
&lt;p&gt;kernel/irq/manage.c:&lt;/p&gt;
&lt;p&gt;/* make sure affinity_hint is cleaned up */
	if (WARN_ON_ONCE(desc-&amp;gt;affinity_hint))
		desc-&amp;gt;affinity_hint = NULL;&lt;/p&gt;
&lt;p&gt;So to fix this issue, clear the IRQ affinity hint before calling
ath12k_pci_free_irq() in the error path. The affinity will be cleared once
again further down the error path due to code organization, but that does
no harm.&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;wifi: ath12k: Clear affinity hint before calling ath12k_pci_free_irq() in error path&lt;/p&gt;
&lt;p&gt;If a shared IRQ is used by the driver due to platform limitation, then the
IRQ affinity hint is set right after the allocation of IRQ vectors in
ath12k_pci_msi_alloc(). This does no harm unless one of the functions
requesting the IRQ fails and attempt to free the IRQ.&lt;/p&gt;
&lt;p&gt;This may end up with a warning from the IRQ core that is expecting the
affinity hint to be cleared before freeing the IRQ:&lt;/p&gt;
&lt;p&gt;kernel/irq/manage.c:&lt;/p&gt;
&lt;p&gt;/* make sure affinity_hint is cleaned up */
	if (WARN_ON_ONCE(desc-&amp;gt;affinity_hint))
		desc-&amp;gt;affinity_hint = NULL;&lt;/p&gt;
&lt;p&gt;So to fix this issue, clear the IRQ affinity hint before calling
ath12k_pci_free_irq() in the error path. The affinity will be cleared once
again further down the error path due to code organization, but that does
no harm.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-22128</guid>
    </item>
    <item>
      <title>GHSA-2w3p-68xj-4hh5</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2w3p-68xj-4hh5</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: ath12k: Clear affinity hint before calling ath12k_pci_free_irq() in error path&lt;/p&gt;
&lt;p&gt;If a shared IRQ is used by the driver due to platform limitation, then the
IRQ affinity hint is set right after the allocation of IRQ vectors in
ath12k_pci_msi_alloc(). This does no harm unless one of the functions
requesting the IRQ fails and attempt to free the IRQ.&lt;/p&gt;
&lt;p&gt;This may end up with a warning from the IRQ core that is expecting the
affinity hint to be cleared before freeing the IRQ:&lt;/p&gt;
&lt;p&gt;kernel/irq/manage.c:&lt;/p&gt;
&lt;p&gt;/* make sure affinity_hint is cleaned up */
	if (WARN_ON_ONCE(desc-&amp;gt;affinity_hint))
		desc-&amp;gt;affinity_hint = NULL;&lt;/p&gt;
&lt;p&gt;So to fix this issue, clear the IRQ affinity hint before calling
ath12k_pci_free_irq() in the error path. The affinity will be cleared once
again further down the error path due to code organization, but that does
no harm.&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;wifi: ath12k: Clear affinity hint before calling ath12k_pci_free_irq() in error path&lt;/p&gt;
&lt;p&gt;If a shared IRQ is used by the driver due to platform limitation, then the
IRQ affinity hint is set right after the allocation of IRQ vectors in
ath12k_pci_msi_alloc(). This does no harm unless one of the functions
requesting the IRQ fails and attempt to free the IRQ.&lt;/p&gt;
&lt;p&gt;This may end up with a warning from the IRQ core that is expecting the
affinity hint to be cleared before freeing the IRQ:&lt;/p&gt;
&lt;p&gt;kernel/irq/manage.c:&lt;/p&gt;
&lt;p&gt;/* make sure affinity_hint is cleaned up */
	if (WARN_ON_ONCE(desc-&amp;gt;affinity_hint))
		desc-&amp;gt;affinity_hint = NULL;&lt;/p&gt;
&lt;p&gt;So to fix this issue, clear the IRQ affinity hint before calling
ath12k_pci_free_irq() in the error path. The affinity will be cleared once
again further down the error path due to code organization, but that does
no harm.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2w3p-68xj-4hh5</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01614-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01614-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:01614-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-22128</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-22128</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 114 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: Clear affinity hint before calling ath12k_pci_free_irq() in error path If a shared IRQ is used by the driver due to platform limitation, then the IRQ affinity hint is set right after the allocation of IRQ vectors in ath12k_pci_msi_alloc(). This does no harm unless one of the functions requesting the IRQ fails and attempt to free the IRQ. This may end up with a warning from the IRQ core that is expecting the affinity hint to be cleared before freeing the IRQ: kernel/irq/manage.c: 	/* make sure affinity_hint is cleaned up */ 	if (WARN_ON_ONCE(desc-&amp;gt;affinity_hint)) 		desc-&amp;gt;affinity_hint = NULL; So to fix this issue, clear the IRQ affinity hint before calling ath12k_pci_free_irq() in the error path. The affinity will be cleared once again further down the error path due to code organization, but that does no harm.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 114 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: Clear affinity hint before calling ath12k_pci_free_irq() in error path If a shared IRQ is used by the driver due to platform limitation, then the IRQ affinity hint is set right after the allocation of IRQ vectors in ath12k_pci_msi_alloc(). This does no harm unless one of the functions requesting the IRQ fails and attempt to free the IRQ. This may end up with a warning from the IRQ core that is expecting the affinity hint to be cleared before freeing the IRQ: kernel/irq/manage.c: 	/* make sure affinity_hint is cleaned up */ 	if (WARN_ON_ONCE(desc-&amp;gt;affinity_hint)) 		desc-&amp;gt;affinity_hint = NULL; So to fix this issue, clear the IRQ affinity hint before calling ath12k_pci_free_irq() in the error path. The affinity will be cleared once again further down the error path due to code organization, but that does no harm.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-22128</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0844 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0844</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht genauer beschriebene Auswirkungen erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht genauer beschriebene Auswirkungen erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0844</guid>
    </item>
  </channel>
</rss>
