<?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 16:35:06 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-46042</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-46042</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-46042</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0831 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0831</link>
      <description>certfr-2026-avi-0831</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0831</guid>
    </item>
    <item>
      <title>EUVD-2026-327095</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-327095</link>
      <description>EUVD-2026-327095</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-327095</guid>
    </item>
    <item>
      <title>fkie_cve-2026-46042</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-46042</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/mempolicy: fix memory leaks in weighted_interleave_auto_store()&lt;/p&gt;
&lt;p&gt;weighted_interleave_auto_store() fetches old_wi_state inside the if
(!input) block only.  This causes two memory leaks:&lt;/p&gt;
&lt;p&gt;1. When a user writes &amp;#34;false&amp;#34; and the current mode is already manual,
   the function returns early without freeing the freshly allocated
   new_wi_state.&lt;/p&gt;
&lt;p&gt;2. When a user writes &amp;#34;true&amp;#34;, old_wi_state stays NULL because the
   fetch is skipped entirely. The old state is then overwritten by
   rcu_assign_pointer() but never freed, since the cleanup path is
   gated on old_wi_state being non-NULL. A user can trigger this
   repeatedly by writing &amp;#34;1&amp;#34; in a loop.&lt;/p&gt;
&lt;p&gt;Fix both leaks by moving the old_wi_state fetch before the input check,
making it unconditional.  This also allows a unified early return for both
&amp;#34;true&amp;#34; and &amp;#34;false&amp;#34; when the requested mode matches the current mode.&lt;/p&gt;
&lt;p&gt;Reviewed by: Donet Tom &amp;lt;donettom@linux.ibm.com&amp;gt;&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;mm/mempolicy: fix memory leaks in weighted_interleave_auto_store()&lt;/p&gt;
&lt;p&gt;weighted_interleave_auto_store() fetches old_wi_state inside the if
(!input) block only.  This causes two memory leaks:&lt;/p&gt;
&lt;p&gt;1. When a user writes &amp;#34;false&amp;#34; and the current mode is already manual,
   the function returns early without freeing the freshly allocated
   new_wi_state.&lt;/p&gt;
&lt;p&gt;2. When a user writes &amp;#34;true&amp;#34;, old_wi_state stays NULL because the
   fetch is skipped entirely. The old state is then overwritten by
   rcu_assign_pointer() but never freed, since the cleanup path is
   gated on old_wi_state being non-NULL. A user can trigger this
   repeatedly by writing &amp;#34;1&amp;#34; in a loop.&lt;/p&gt;
&lt;p&gt;Fix both leaks by moving the old_wi_state fetch before the input check,
making it unconditional.  This also allows a unified early return for both
&amp;#34;true&amp;#34; and &amp;#34;false&amp;#34; when the requested mode matches the current mode.&lt;/p&gt;
&lt;p&gt;Reviewed by: Donet Tom &amp;lt;donettom@linux.ibm.com&amp;gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-46042</guid>
    </item>
    <item>
      <title>GHSA-pmw2-6gh9-j59g</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pmw2-6gh9-j59g</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/mempolicy: fix memory leaks in weighted_interleave_auto_store()&lt;/p&gt;
&lt;p&gt;weighted_interleave_auto_store() fetches old_wi_state inside the if
(!input) block only.  This causes two memory leaks:&lt;/p&gt;
&lt;p&gt;1. When a user writes &amp;#34;false&amp;#34; and the current mode is already manual,
   the function returns early without freeing the freshly allocated
   new_wi_state.&lt;/p&gt;
&lt;p&gt;2. When a user writes &amp;#34;true&amp;#34;, old_wi_state stays NULL because the
   fetch is skipped entirely. The old state is then overwritten by
   rcu_assign_pointer() but never freed, since the cleanup path is
   gated on old_wi_state being non-NULL. A user can trigger this
   repeatedly by writing &amp;#34;1&amp;#34; in a loop.&lt;/p&gt;
&lt;p&gt;Fix both leaks by moving the old_wi_state fetch before the input check,
making it unconditional.  This also allows a unified early return for both
&amp;#34;true&amp;#34; and &amp;#34;false&amp;#34; when the requested mode matches the current mode.&lt;/p&gt;
&lt;p&gt;Reviewed by: Donet Tom &amp;lt;donettom@linux.ibm.com&amp;gt;&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;mm/mempolicy: fix memory leaks in weighted_interleave_auto_store()&lt;/p&gt;
&lt;p&gt;weighted_interleave_auto_store() fetches old_wi_state inside the if
(!input) block only.  This causes two memory leaks:&lt;/p&gt;
&lt;p&gt;1. When a user writes &amp;#34;false&amp;#34; and the current mode is already manual,
   the function returns early without freeing the freshly allocated
   new_wi_state.&lt;/p&gt;
&lt;p&gt;2. When a user writes &amp;#34;true&amp;#34;, old_wi_state stays NULL because the
   fetch is skipped entirely. The old state is then overwritten by
   rcu_assign_pointer() but never freed, since the cleanup path is
   gated on old_wi_state being non-NULL. A user can trigger this
   repeatedly by writing &amp;#34;1&amp;#34; in a loop.&lt;/p&gt;
&lt;p&gt;Fix both leaks by moving the old_wi_state fetch before the input check,
making it unconditional.  This also allows a unified early return for both
&amp;#34;true&amp;#34; and &amp;#34;false&amp;#34; when the requested mode matches the current mode.&lt;/p&gt;
&lt;p&gt;Reviewed by: Donet Tom &amp;lt;donettom@linux.ibm.com&amp;gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pmw2-6gh9-j59g</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:10954-1 — kernel-devel-7.0.11-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1</link>
      <description>&lt;p&gt;kernel-devel-7.0.11-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.0.11-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-46042</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46042</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 116 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/mempolicy: fix memory leaks in weighted_interleave_auto_store() weighted_interleave_auto_store() fetches old_wi_state inside the if (!input) block only.  This causes two memory leaks: 1. When a user writes &amp;#34;false&amp;#34; and the current mode is already manual,    the function returns early without freeing the freshly allocated    new_wi_state. 2. When a user writes &amp;#34;true&amp;#34;, old_wi_state stays NULL because the    fetch is skipped entirely. The old state is then overwritten by    rcu_assign_pointer() but never freed, since the cleanup path is    gated on old_wi_state being non-NULL. A user can trigger this    repeatedly by writing &amp;#34;1&amp;#34; in a loop. Fix both leaks by moving the old_wi_state fetch before the input check, making it unconditional.  This also allows a unified early return for both &amp;#34;true&amp;#34; and &amp;#34;false&amp;#34; when the requested mode matches the current mode. Reviewed by: Donet Tom &amp;lt;donettom@linux.ibm.com&amp;gt;&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 116 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/mempolicy: fix memory leaks in weighted_interleave_auto_store() weighted_interleave_auto_store() fetches old_wi_state inside the if (!input) block only.  This causes two memory leaks: 1. When a user writes &amp;#34;false&amp;#34; and the current mode is already manual,    the function returns early without freeing the freshly allocated    new_wi_state. 2. When a user writes &amp;#34;true&amp;#34;, old_wi_state stays NULL because the    fetch is skipped entirely. The old state is then overwritten by    rcu_assign_pointer() but never freed, since the cleanup path is    gated on old_wi_state being non-NULL. A user can trigger this    repeatedly by writing &amp;#34;1&amp;#34; in a loop. Fix both leaks by moving the old_wi_state fetch before the input check, making it unconditional.  This also allows a unified early return for both &amp;#34;true&amp;#34; and &amp;#34;false&amp;#34; when the requested mode matches the current mode. Reviewed by: Donet Tom &amp;lt;donettom@linux.ibm.com&amp;gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46042</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1700 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700</guid>
    </item>
  </channel>
</rss>
