<?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 14:02:28 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74372</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-74372</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-74372</guid>
    </item>
    <item>
      <title>EUVD-2026-353843</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-353843</link>
      <description>EUVD-2026-353843</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-353843</guid>
    </item>
    <item>
      <title>fkie_cve-2026-74372</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-74372</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;raid1: fix nr_pending leak in REQ_ATOMIC bad-block error path&lt;/p&gt;
&lt;p&gt;In raid1_write_request(), each per-mirror loop iteration begins by
incrementing rdev-&amp;gt;nr_pending. If a REQ_ATOMIC write encounters a
badblock within the requested range, the code jumps to err_handle
without dropping the reference taken for the current mirror.&lt;/p&gt;
&lt;p&gt;err_handle&amp;#39;s cleanup loop will only decrements for k &amp;lt; i and
r1_bio-&amp;gt;bios[k] is non-NULL. The current slot is therefore skipped,
leaving its nr_pending reference leaked permanently. The reference
prevents the rdev from ever being removed, since raid1_remove_conf()
refuses to remove an rdev with nr_pending &amp;gt; 0.&lt;/p&gt;
&lt;p&gt;Fix this by calling rdev_dec_pending() before jumping to err_handle.&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;raid1: fix nr_pending leak in REQ_ATOMIC bad-block error path&lt;/p&gt;
&lt;p&gt;In raid1_write_request(), each per-mirror loop iteration begins by
incrementing rdev-&amp;gt;nr_pending. If a REQ_ATOMIC write encounters a
badblock within the requested range, the code jumps to err_handle
without dropping the reference taken for the current mirror.&lt;/p&gt;
&lt;p&gt;err_handle&amp;#39;s cleanup loop will only decrements for k &amp;lt; i and
r1_bio-&amp;gt;bios[k] is non-NULL. The current slot is therefore skipped,
leaving its nr_pending reference leaked permanently. The reference
prevents the rdev from ever being removed, since raid1_remove_conf()
refuses to remove an rdev with nr_pending &amp;gt; 0.&lt;/p&gt;
&lt;p&gt;Fix this by calling rdev_dec_pending() before jumping to err_handle.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-74372</guid>
    </item>
    <item>
      <title>GHSA-g6g3-325w-fc52</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-g6g3-325w-fc52</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;raid1: fix nr_pending leak in REQ_ATOMIC bad-block error path&lt;/p&gt;
&lt;p&gt;In raid1_write_request(), each per-mirror loop iteration begins by
incrementing rdev-&amp;gt;nr_pending. If a REQ_ATOMIC write encounters a
badblock within the requested range, the code jumps to err_handle
without dropping the reference taken for the current mirror.&lt;/p&gt;
&lt;p&gt;err_handle&amp;#39;s cleanup loop will only decrements for k &amp;lt; i and
r1_bio-&amp;gt;bios[k] is non-NULL. The current slot is therefore skipped,
leaving its nr_pending reference leaked permanently. The reference
prevents the rdev from ever being removed, since raid1_remove_conf()
refuses to remove an rdev with nr_pending &amp;gt; 0.&lt;/p&gt;
&lt;p&gt;Fix this by calling rdev_dec_pending() before jumping to err_handle.&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;raid1: fix nr_pending leak in REQ_ATOMIC bad-block error path&lt;/p&gt;
&lt;p&gt;In raid1_write_request(), each per-mirror loop iteration begins by
incrementing rdev-&amp;gt;nr_pending. If a REQ_ATOMIC write encounters a
badblock within the requested range, the code jumps to err_handle
without dropping the reference taken for the current mirror.&lt;/p&gt;
&lt;p&gt;err_handle&amp;#39;s cleanup loop will only decrements for k &amp;lt; i and
r1_bio-&amp;gt;bios[k] is non-NULL. The current slot is therefore skipped,
leaving its nr_pending reference leaked permanently. The reference
prevents the rdev from ever being removed, since raid1_remove_conf()
refuses to remove an rdev with nr_pending &amp;gt; 0.&lt;/p&gt;
&lt;p&gt;Fix this by calling rdev_dec_pending() before jumping to err_handle.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-g6g3-325w-fc52</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74372</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74372</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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: raid1: fix nr_pending leak in REQ_ATOMIC bad-block error path In raid1_write_request(), each per-mirror loop iteration begins by incrementing rdev-&amp;gt;nr_pending. If a REQ_ATOMIC write encounters a badblock within the requested range, the code jumps to err_handle without dropping the reference taken for the current mirror. err_handle&amp;#39;s cleanup loop will only decrements for k &amp;lt; i and r1_bio-&amp;gt;bios[k] is non-NULL. The current slot is therefore skipped, leaving its nr_pending reference leaked permanently. The reference prevents the rdev from ever being removed, since raid1_remove_conf() refuses to remove an rdev with nr_pending &amp;gt; 0. Fix this by calling rdev_dec_pending() before jumping to err_handle.&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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: raid1: fix nr_pending leak in REQ_ATOMIC bad-block error path In raid1_write_request(), each per-mirror loop iteration begins by incrementing rdev-&amp;gt;nr_pending. If a REQ_ATOMIC write encounters a badblock within the requested range, the code jumps to err_handle without dropping the reference taken for the current mirror. err_handle&amp;#39;s cleanup loop will only decrements for k &amp;lt; i and r1_bio-&amp;gt;bios[k] is non-NULL. The current slot is therefore skipped, leaving its nr_pending reference leaked permanently. The reference prevents the rdev from ever being removed, since raid1_remove_conf() refuses to remove an rdev with nr_pending &amp;gt; 0. Fix this by calling rdev_dec_pending() before jumping to err_handle.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74372</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
