<?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 07:50:50 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-46130</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-46130</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-46130</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — 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-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>EUVD-2026-343612</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-343612</link>
      <description>EUVD-2026-343612</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-343612</guid>
    </item>
    <item>
      <title>fkie_cve-2026-46130</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-46130</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dm-verity-fec: fix reading parity bytes split across blocks (take 3)&lt;/p&gt;
&lt;p&gt;fec_decode_bufs() assumes that the parity bytes of the first RS codeword
it decodes are never split across parity blocks.&lt;/p&gt;
&lt;p&gt;This assumption is false.  Consider v-&amp;gt;fec-&amp;gt;block_size == 4096 &amp;amp;&amp;amp;
v-&amp;gt;fec-&amp;gt;roots == 17 &amp;amp;&amp;amp; fio-&amp;gt;nbufs == 1, for example.  In that case, each
call to fec_decode_bufs() consumes v-&amp;gt;fec-&amp;gt;roots * (fio-&amp;gt;nbufs &amp;lt;&amp;lt;
DM_VERITY_FEC_BUF_RS_BITS) = 272 parity bytes.&lt;/p&gt;
&lt;p&gt;Considering that the parity data for each message block starts on a
block boundary, the byte alignment in the parity data will iterate
through 272*i mod 4096 until the 3 parity blocks have been consumed.  On
the 16th call (i=15), the alignment will be 4080 bytes into the first
block.  Only 16 bytes remain in that block, but 17 parity bytes will be
needed.  The code reads out-of-bounds from the parity block buffer.&lt;/p&gt;
&lt;p&gt;Fortunately this doesn&amp;#39;t normally happen, since it can occur only for
certain non-default values of fec_roots *and* when the maximum number of
buffers couldn&amp;#39;t be allocated due to low memory.  For example with
block_size=4096 only the following cases are affected:&lt;/p&gt;
&lt;p&gt;fec_roots=17: nbufs in [1, 3, 5, 15]
    fec_roots=19: nbufs in [1, 229]
    fec_roots=21: nbufs in [1, 3, 5, 13, 15, 39, 65, 195]
    fec_roots=23: nbufs in [1, 89]&lt;/p&gt;
&lt;p&gt;Regardless, fix it by refactoring how the parity blocks are read.&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;dm-verity-fec: fix reading parity bytes split across blocks (take 3)&lt;/p&gt;
&lt;p&gt;fec_decode_bufs() assumes that the parity bytes of the first RS codeword
it decodes are never split across parity blocks.&lt;/p&gt;
&lt;p&gt;This assumption is false.  Consider v-&amp;gt;fec-&amp;gt;block_size == 4096 &amp;amp;&amp;amp;
v-&amp;gt;fec-&amp;gt;roots == 17 &amp;amp;&amp;amp; fio-&amp;gt;nbufs == 1, for example.  In that case, each
call to fec_decode_bufs() consumes v-&amp;gt;fec-&amp;gt;roots * (fio-&amp;gt;nbufs &amp;lt;&amp;lt;
DM_VERITY_FEC_BUF_RS_BITS) = 272 parity bytes.&lt;/p&gt;
&lt;p&gt;Considering that the parity data for each message block starts on a
block boundary, the byte alignment in the parity data will iterate
through 272*i mod 4096 until the 3 parity blocks have been consumed.  On
the 16th call (i=15), the alignment will be 4080 bytes into the first
block.  Only 16 bytes remain in that block, but 17 parity bytes will be
needed.  The code reads out-of-bounds from the parity block buffer.&lt;/p&gt;
&lt;p&gt;Fortunately this doesn&amp;#39;t normally happen, since it can occur only for
certain non-default values of fec_roots *and* when the maximum number of
buffers couldn&amp;#39;t be allocated due to low memory.  For example with
block_size=4096 only the following cases are affected:&lt;/p&gt;
&lt;p&gt;fec_roots=17: nbufs in [1, 3, 5, 15]
    fec_roots=19: nbufs in [1, 229]
    fec_roots=21: nbufs in [1, 3, 5, 13, 15, 39, 65, 195]
    fec_roots=23: nbufs in [1, 89]&lt;/p&gt;
&lt;p&gt;Regardless, fix it by refactoring how the parity blocks are read.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-46130</guid>
    </item>
    <item>
      <title>GHSA-6hvc-rwfc-mp4j</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6hvc-rwfc-mp4j</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dm-verity-fec: fix reading parity bytes split across blocks (take 3)&lt;/p&gt;
&lt;p&gt;fec_decode_bufs() assumes that the parity bytes of the first RS codeword
it decodes are never split across parity blocks.&lt;/p&gt;
&lt;p&gt;This assumption is false.  Consider v-&amp;gt;fec-&amp;gt;block_size == 4096 &amp;amp;&amp;amp;
v-&amp;gt;fec-&amp;gt;roots == 17 &amp;amp;&amp;amp; fio-&amp;gt;nbufs == 1, for example.  In that case, each
call to fec_decode_bufs() consumes v-&amp;gt;fec-&amp;gt;roots * (fio-&amp;gt;nbufs &amp;lt;&amp;lt;
DM_VERITY_FEC_BUF_RS_BITS) = 272 parity bytes.&lt;/p&gt;
&lt;p&gt;Considering that the parity data for each message block starts on a
block boundary, the byte alignment in the parity data will iterate
through 272*i mod 4096 until the 3 parity blocks have been consumed.  On
the 16th call (i=15), the alignment will be 4080 bytes into the first
block.  Only 16 bytes remain in that block, but 17 parity bytes will be
needed.  The code reads out-of-bounds from the parity block buffer.&lt;/p&gt;
&lt;p&gt;Fortunately this doesn&amp;#39;t normally happen, since it can occur only for
certain non-default values of fec_roots *and* when the maximum number of
buffers couldn&amp;#39;t be allocated due to low memory.  For example with
block_size=4096 only the following cases are affected:&lt;/p&gt;
&lt;p&gt;fec_roots=17: nbufs in [1, 3, 5, 15]
    fec_roots=19: nbufs in [1, 229]
    fec_roots=21: nbufs in [1, 3, 5, 13, 15, 39, 65, 195]
    fec_roots=23: nbufs in [1, 89]&lt;/p&gt;
&lt;p&gt;Regardless, fix it by refactoring how the parity blocks are read.&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;dm-verity-fec: fix reading parity bytes split across blocks (take 3)&lt;/p&gt;
&lt;p&gt;fec_decode_bufs() assumes that the parity bytes of the first RS codeword
it decodes are never split across parity blocks.&lt;/p&gt;
&lt;p&gt;This assumption is false.  Consider v-&amp;gt;fec-&amp;gt;block_size == 4096 &amp;amp;&amp;amp;
v-&amp;gt;fec-&amp;gt;roots == 17 &amp;amp;&amp;amp; fio-&amp;gt;nbufs == 1, for example.  In that case, each
call to fec_decode_bufs() consumes v-&amp;gt;fec-&amp;gt;roots * (fio-&amp;gt;nbufs &amp;lt;&amp;lt;
DM_VERITY_FEC_BUF_RS_BITS) = 272 parity bytes.&lt;/p&gt;
&lt;p&gt;Considering that the parity data for each message block starts on a
block boundary, the byte alignment in the parity data will iterate
through 272*i mod 4096 until the 3 parity blocks have been consumed.  On
the 16th call (i=15), the alignment will be 4080 bytes into the first
block.  Only 16 bytes remain in that block, but 17 parity bytes will be
needed.  The code reads out-of-bounds from the parity block buffer.&lt;/p&gt;
&lt;p&gt;Fortunately this doesn&amp;#39;t normally happen, since it can occur only for
certain non-default values of fec_roots *and* when the maximum number of
buffers couldn&amp;#39;t be allocated due to low memory.  For example with
block_size=4096 only the following cases are affected:&lt;/p&gt;
&lt;p&gt;fec_roots=17: nbufs in [1, 3, 5, 15]
    fec_roots=19: nbufs in [1, 229]
    fec_roots=21: nbufs in [1, 3, 5, 13, 15, 39, 65, 195]
    fec_roots=23: nbufs in [1, 89]&lt;/p&gt;
&lt;p&gt;Regardless, fix it by refactoring how the parity blocks are read.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6hvc-rwfc-mp4j</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-46130 — dm-verity-fec: fix reading parity bytes split across blocks (take 3)</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-46130</link>
      <description>msrc_CVE-2026-46130</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-46130</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>SUSE-SU-2026:23066-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23066-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:23066-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-46130</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46130</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 162 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dm-verity-fec: fix reading parity bytes split across blocks (take 3) fec_decode_bufs() assumes that the parity bytes of the first RS codeword it decodes are never split across parity blocks. This assumption is false.  Consider v-&amp;gt;fec-&amp;gt;block_size == 4096 &amp;amp;&amp;amp; v-&amp;gt;fec-&amp;gt;roots == 17 &amp;amp;&amp;amp; fio-&amp;gt;nbufs == 1, for example.  In that case, each call to fec_decode_bufs() consumes v-&amp;gt;fec-&amp;gt;roots * (fio-&amp;gt;nbufs &amp;lt;&amp;lt; DM_VERITY_FEC_BUF_RS_BITS) = 272 parity bytes. Considering that the parity data for each message block starts on a block boundary, the byte alignment in the parity data will iterate through 272*i mod 4096 until the 3 parity blocks have been consumed.  On the 16th call (i=15), the alignment will be 4080 bytes into the first block.  Only 16 bytes remain in that block, but 17 parity bytes will be needed.  The code reads out-of-bounds from the parity block buffer. Fortunately this doesn&amp;#39;t normally happen, since it can occur only for certain non-default values of fec_roots *and* when the maximum number of buffers couldn&amp;#39;t be allocated due to low memory.  For example with block_size=4096 only the following cases are affected:     fec_roots=17: nbufs in [1, 3, 5, 15]     fec_roots=19: nbufs in [1, 229]     fec_roots=21: nbufs in [1, 3, 5, 13, 15, 39, 65, 195]     fec_roots=23: nbufs in [1, 89] Regardless, fix it by refactoring how the parity blocks are read.&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 162 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dm-verity-fec: fix reading parity bytes split across blocks (take 3) fec_decode_bufs() assumes that the parity bytes of the first RS codeword it decodes are never split across parity blocks. This assumption is false.  Consider v-&amp;gt;fec-&amp;gt;block_size == 4096 &amp;amp;&amp;amp; v-&amp;gt;fec-&amp;gt;roots == 17 &amp;amp;&amp;amp; fio-&amp;gt;nbufs == 1, for example.  In that case, each call to fec_decode_bufs() consumes v-&amp;gt;fec-&amp;gt;roots * (fio-&amp;gt;nbufs &amp;lt;&amp;lt; DM_VERITY_FEC_BUF_RS_BITS) = 272 parity bytes. Considering that the parity data for each message block starts on a block boundary, the byte alignment in the parity data will iterate through 272*i mod 4096 until the 3 parity blocks have been consumed.  On the 16th call (i=15), the alignment will be 4080 bytes into the first block.  Only 16 bytes remain in that block, but 17 parity bytes will be needed.  The code reads out-of-bounds from the parity block buffer. Fortunately this doesn&amp;#39;t normally happen, since it can occur only for certain non-default values of fec_roots *and* when the maximum number of buffers couldn&amp;#39;t be allocated due to low memory.  For example with block_size=4096 only the following cases are affected:     fec_roots=17: nbufs in [1, 3, 5, 15]     fec_roots=19: nbufs in [1, 229]     fec_roots=21: nbufs in [1, 3, 5, 13, 15, 39, 65, 195]     fec_roots=23: nbufs in [1, 89] Regardless, fix it by refactoring how the parity blocks are read.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46130</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>
