<?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:57:54 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-43066</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-43066</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://cve.radiocsirt.org/vuln/bell-cve-2026-43066</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0696 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0696</link>
      <description>certfr-2026-avi-0696</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0696</guid>
    </item>
    <item>
      <title>EUVD-2026-315733</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-315733</link>
      <description>EUVD-2026-315733</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-315733</guid>
    </item>
    <item>
      <title>fkie_cve-2026-43066</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-43066</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ext4: fix iloc.bh leak in ext4_fc_replay_inode() error paths&lt;/p&gt;
&lt;p&gt;During code review, Joseph found that ext4_fc_replay_inode() calls
ext4_get_fc_inode_loc() to get the inode location, which holds a
reference to iloc.bh that must be released via brelse().&lt;/p&gt;
&lt;p&gt;However, several error paths jump to the &amp;#39;out&amp;#39; label without
releasing iloc.bh:&lt;/p&gt;
&lt;p&gt;- ext4_handle_dirty_metadata() failure
 - sync_dirty_buffer() failure
 - ext4_mark_inode_used() failure
 - ext4_iget() failure&lt;/p&gt;
&lt;p&gt;Fix this by introducing an &amp;#39;out_brelse&amp;#39; label placed just before
the existing &amp;#39;out&amp;#39; label to ensure iloc.bh is always released.&lt;/p&gt;
&lt;p&gt;Additionally, make ext4_fc_replay_inode() propagate errors
properly instead of always returning 0.&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;ext4: fix iloc.bh leak in ext4_fc_replay_inode() error paths&lt;/p&gt;
&lt;p&gt;During code review, Joseph found that ext4_fc_replay_inode() calls
ext4_get_fc_inode_loc() to get the inode location, which holds a
reference to iloc.bh that must be released via brelse().&lt;/p&gt;
&lt;p&gt;However, several error paths jump to the &amp;#39;out&amp;#39; label without
releasing iloc.bh:&lt;/p&gt;
&lt;p&gt;- ext4_handle_dirty_metadata() failure
 - sync_dirty_buffer() failure
 - ext4_mark_inode_used() failure
 - ext4_iget() failure&lt;/p&gt;
&lt;p&gt;Fix this by introducing an &amp;#39;out_brelse&amp;#39; label placed just before
the existing &amp;#39;out&amp;#39; label to ensure iloc.bh is always released.&lt;/p&gt;
&lt;p&gt;Additionally, make ext4_fc_replay_inode() propagate errors
properly instead of always returning 0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-43066</guid>
    </item>
    <item>
      <title>GHSA-vqp8-9648-3qfh</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vqp8-9648-3qfh</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ext4: fix iloc.bh leak in ext4_fc_replay_inode() error paths&lt;/p&gt;
&lt;p&gt;During code review, Joseph found that ext4_fc_replay_inode() calls
ext4_get_fc_inode_loc() to get the inode location, which holds a
reference to iloc.bh that must be released via brelse().&lt;/p&gt;
&lt;p&gt;However, several error paths jump to the &amp;#39;out&amp;#39; label without
releasing iloc.bh:&lt;/p&gt;
&lt;p&gt;- ext4_handle_dirty_metadata() failure
 - sync_dirty_buffer() failure
 - ext4_mark_inode_used() failure
 - ext4_iget() failure&lt;/p&gt;
&lt;p&gt;Fix this by introducing an &amp;#39;out_brelse&amp;#39; label placed just before
the existing &amp;#39;out&amp;#39; label to ensure iloc.bh is always released.&lt;/p&gt;
&lt;p&gt;Additionally, make ext4_fc_replay_inode() propagate errors
properly instead of always returning 0.&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;ext4: fix iloc.bh leak in ext4_fc_replay_inode() error paths&lt;/p&gt;
&lt;p&gt;During code review, Joseph found that ext4_fc_replay_inode() calls
ext4_get_fc_inode_loc() to get the inode location, which holds a
reference to iloc.bh that must be released via brelse().&lt;/p&gt;
&lt;p&gt;However, several error paths jump to the &amp;#39;out&amp;#39; label without
releasing iloc.bh:&lt;/p&gt;
&lt;p&gt;- ext4_handle_dirty_metadata() failure
 - sync_dirty_buffer() failure
 - ext4_mark_inode_used() failure
 - ext4_iget() failure&lt;/p&gt;
&lt;p&gt;Fix this by introducing an &amp;#39;out_brelse&amp;#39; label placed just before
the existing &amp;#39;out&amp;#39; label to ensure iloc.bh is always released.&lt;/p&gt;
&lt;p&gt;Additionally, make ext4_fc_replay_inode() propagate errors
properly instead of always returning 0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vqp8-9648-3qfh</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:20965-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:20965-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:20965-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:22099-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:22099-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:22099-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-43066</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43066</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 179 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ext4: fix iloc.bh leak in ext4_fc_replay_inode() error paths During code review, Joseph found that ext4_fc_replay_inode() calls ext4_get_fc_inode_loc() to get the inode location, which holds a reference to iloc.bh that must be released via brelse(). However, several error paths jump to the &amp;#39;out&amp;#39; label without releasing iloc.bh:  - ext4_handle_dirty_metadata() failure  - sync_dirty_buffer() failure  - ext4_mark_inode_used() failure  - ext4_iget() failure Fix this by introducing an &amp;#39;out_brelse&amp;#39; label placed just before the existing &amp;#39;out&amp;#39; label to ensure iloc.bh is always released. Additionally, make ext4_fc_replay_inode() propagate errors properly instead of always returning 0.&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 179 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ext4: fix iloc.bh leak in ext4_fc_replay_inode() error paths During code review, Joseph found that ext4_fc_replay_inode() calls ext4_get_fc_inode_loc() to get the inode location, which holds a reference to iloc.bh that must be released via brelse(). However, several error paths jump to the &amp;#39;out&amp;#39; label without releasing iloc.bh:  - ext4_handle_dirty_metadata() failure  - sync_dirty_buffer() failure  - ext4_mark_inode_used() failure  - ext4_iget() failure Fix this by introducing an &amp;#39;out_brelse&amp;#39; label placed just before the existing &amp;#39;out&amp;#39; label to ensure iloc.bh is always released. Additionally, make ext4_fc_replay_inode() propagate errors properly instead of always returning 0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43066</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1385 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1385</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Informationen offenzulegen, Sicherheitsmaßnahmen zu umgehen oder potentiell beliebigen Programmcode auszuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Informationen offenzulegen, Sicherheitsmaßnahmen zu umgehen oder potentiell beliebigen Programmcode auszuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1385</guid>
    </item>
  </channel>
</rss>
