<?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 20:41:02 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03176</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03176</link>
      <description>bdu:2026-03176</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03176</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-71135</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-71135</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-2025-71135</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0166 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0166</link>
      <description>certfr-2026-avi-0166</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0166</guid>
    </item>
    <item>
      <title>EUVD-2026-320922</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-320922</link>
      <description>EUVD-2026-320922</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-320922</guid>
    </item>
    <item>
      <title>fkie_cve-2025-71135</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-71135</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt()&lt;/p&gt;
&lt;p&gt;The variable mddev-&amp;gt;private is first assigned to conf and then checked:&lt;/p&gt;
&lt;p&gt;conf = mddev-&amp;gt;private;
  if (!conf) ...&lt;/p&gt;
&lt;p&gt;If conf is NULL, then mddev-&amp;gt;private is also NULL. In this case,
null-pointer dereferences can occur when calling raid5_quiesce():&lt;/p&gt;
&lt;p&gt;raid5_quiesce(mddev, true);
  raid5_quiesce(mddev, false);&lt;/p&gt;
&lt;p&gt;since mddev-&amp;gt;private is assigned to conf again in raid5_quiesce(), and conf
is dereferenced in several places, for example:&lt;/p&gt;
&lt;p&gt;conf-&amp;gt;quiesce = 0;
  wake_up(&amp;amp;conf-&amp;gt;wait_for_quiescent);&lt;/p&gt;
&lt;p&gt;To fix this issue, the function should unlock mddev and return before
invoking raid5_quiesce() when conf is NULL, following the existing pattern
in raid5_change_consistency_policy().&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;md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt()&lt;/p&gt;
&lt;p&gt;The variable mddev-&amp;gt;private is first assigned to conf and then checked:&lt;/p&gt;
&lt;p&gt;conf = mddev-&amp;gt;private;
  if (!conf) ...&lt;/p&gt;
&lt;p&gt;If conf is NULL, then mddev-&amp;gt;private is also NULL. In this case,
null-pointer dereferences can occur when calling raid5_quiesce():&lt;/p&gt;
&lt;p&gt;raid5_quiesce(mddev, true);
  raid5_quiesce(mddev, false);&lt;/p&gt;
&lt;p&gt;since mddev-&amp;gt;private is assigned to conf again in raid5_quiesce(), and conf
is dereferenced in several places, for example:&lt;/p&gt;
&lt;p&gt;conf-&amp;gt;quiesce = 0;
  wake_up(&amp;amp;conf-&amp;gt;wait_for_quiescent);&lt;/p&gt;
&lt;p&gt;To fix this issue, the function should unlock mddev and return before
invoking raid5_quiesce() when conf is NULL, following the existing pattern
in raid5_change_consistency_policy().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-71135</guid>
    </item>
    <item>
      <title>GHSA-w8wp-w464-6xr8</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w8wp-w464-6xr8</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt()&lt;/p&gt;
&lt;p&gt;The variable mddev-&amp;gt;private is first assigned to conf and then checked:&lt;/p&gt;
&lt;p&gt;conf = mddev-&amp;gt;private;
  if (!conf) ...&lt;/p&gt;
&lt;p&gt;If conf is NULL, then mddev-&amp;gt;private is also NULL. In this case,
null-pointer dereferences can occur when calling raid5_quiesce():&lt;/p&gt;
&lt;p&gt;raid5_quiesce(mddev, true);
  raid5_quiesce(mddev, false);&lt;/p&gt;
&lt;p&gt;since mddev-&amp;gt;private is assigned to conf again in raid5_quiesce(), and conf
is dereferenced in several places, for example:&lt;/p&gt;
&lt;p&gt;conf-&amp;gt;quiesce = 0;
  wake_up(&amp;amp;conf-&amp;gt;wait_for_quiescent);&lt;/p&gt;
&lt;p&gt;To fix this issue, the function should unlock mddev and return before
invoking raid5_quiesce() when conf is NULL, following the existing pattern
in raid5_change_consistency_policy().&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;md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt()&lt;/p&gt;
&lt;p&gt;The variable mddev-&amp;gt;private is first assigned to conf and then checked:&lt;/p&gt;
&lt;p&gt;conf = mddev-&amp;gt;private;
  if (!conf) ...&lt;/p&gt;
&lt;p&gt;If conf is NULL, then mddev-&amp;gt;private is also NULL. In this case,
null-pointer dereferences can occur when calling raid5_quiesce():&lt;/p&gt;
&lt;p&gt;raid5_quiesce(mddev, true);
  raid5_quiesce(mddev, false);&lt;/p&gt;
&lt;p&gt;since mddev-&amp;gt;private is assigned to conf again in raid5_quiesce(), and conf
is dereferenced in several places, for example:&lt;/p&gt;
&lt;p&gt;conf-&amp;gt;quiesce = 0;
  wake_up(&amp;amp;conf-&amp;gt;wait_for_quiescent);&lt;/p&gt;
&lt;p&gt;To fix this issue, the function should unlock mddev and return before
invoking raid5_quiesce() when conf is NULL, following the existing pattern
in raid5_change_consistency_policy().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w8wp-w464-6xr8</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:20287-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:20287-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/opensuse-su-2026:20287-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0587-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:0587-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-2026:0587-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-71135</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71135</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 140 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt() The variable mddev-&amp;gt;private is first assigned to conf and then checked:   conf = mddev-&amp;gt;private;   if (!conf) ... If conf is NULL, then mddev-&amp;gt;private is also NULL. In this case, null-pointer dereferences can occur when calling raid5_quiesce():   raid5_quiesce(mddev, true);   raid5_quiesce(mddev, false); since mddev-&amp;gt;private is assigned to conf again in raid5_quiesce(), and conf is dereferenced in several places, for example:   conf-&amp;gt;quiesce = 0;   wake_up(&amp;amp;conf-&amp;gt;wait_for_quiescent); To fix this issue, the function should unlock mddev and return before invoking raid5_quiesce() when conf is NULL, following the existing pattern in raid5_change_consistency_policy().&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 140 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt() The variable mddev-&amp;gt;private is first assigned to conf and then checked:   conf = mddev-&amp;gt;private;   if (!conf) ... If conf is NULL, then mddev-&amp;gt;private is also NULL. In this case, null-pointer dereferences can occur when calling raid5_quiesce():   raid5_quiesce(mddev, true);   raid5_quiesce(mddev, false); since mddev-&amp;gt;private is assigned to conf again in raid5_quiesce(), and conf is dereferenced in several places, for example:   conf-&amp;gt;quiesce = 0;   wake_up(&amp;amp;conf-&amp;gt;wait_for_quiescent); To fix this issue, the function should unlock mddev and return before invoking raid5_quiesce() when conf is NULL, following the existing pattern in raid5_change_consistency_policy().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71135</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0119 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0119</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0119</guid>
    </item>
  </channel>
</rss>
