<?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 10:18:03 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-89720</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-89720</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-89720</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1253 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</link>
      <description>certfr-2026-avi-1253</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</guid>
    </item>
    <item>
      <title>EUVD-2026-367699</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-367699</link>
      <description>EUVD-2026-367699</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-367699</guid>
    </item>
    <item>
      <title>fkie_cve-2026-89720</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-89720</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ubifs: fix out-of-bounds read in signature length check&lt;/p&gt;
&lt;p&gt;ubifs_sb_verify_signature() bounds the on-disk ubifs_sig_node-&amp;gt;len field
before handing the signature payload to verify_pkcs7_signature(), but the
check has the wrong sign:&lt;/p&gt;
&lt;p&gt;if (le32_to_cpu(signode-&amp;gt;len) &amp;gt; snod-&amp;gt;len + sizeof(struct ubifs_sig_node))&lt;/p&gt;
&lt;p&gt;The signature bytes start sizeof(struct ubifs_sig_node) (UBIFS_SIG_NODE_SZ,
64 bytes) into the node, so the payload is at most&lt;/p&gt;
&lt;p&gt;snod-&amp;gt;len - sizeof(struct ubifs_sig_node)&lt;/p&gt;
&lt;p&gt;bytes long. Adding the header size instead of subtracting it accepts a
declared length up to 2 * UBIFS_SIG_NODE_SZ larger than the node actually
holds -- past the end of c-&amp;gt;sbuf, which is vmalloc(c-&amp;gt;leb_size).
verify_pkcs7_signature() -&amp;gt; pkcs7_parse_message() -&amp;gt; asn1_ber_decoder()
is then handed that inflated length and reads beyond the allocation while
walking the DER headers. The node length comes straight from the mounted
image, so a crafted signed UBIFS image reaches this via
ubifs_read_superblock() before the signature is cryptographically checked.&lt;/p&gt;
&lt;p&gt;snod-&amp;gt;len is guaranteed to be &amp;gt;= UBIFS_SIG_NODE_SZ by the node scanner
(c-&amp;gt;ranges[UBIFS_SIG_NODE].min_len == UBIFS_SIG_NODE_SZ), so the corrected
subtraction cannot underflow. Legitimately signed images are unaffected: a
correct superblock never declares a signature longer than the node it is
embedded in.&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;ubifs: fix out-of-bounds read in signature length check&lt;/p&gt;
&lt;p&gt;ubifs_sb_verify_signature() bounds the on-disk ubifs_sig_node-&amp;gt;len field
before handing the signature payload to verify_pkcs7_signature(), but the
check has the wrong sign:&lt;/p&gt;
&lt;p&gt;if (le32_to_cpu(signode-&amp;gt;len) &amp;gt; snod-&amp;gt;len + sizeof(struct ubifs_sig_node))&lt;/p&gt;
&lt;p&gt;The signature bytes start sizeof(struct ubifs_sig_node) (UBIFS_SIG_NODE_SZ,
64 bytes) into the node, so the payload is at most&lt;/p&gt;
&lt;p&gt;snod-&amp;gt;len - sizeof(struct ubifs_sig_node)&lt;/p&gt;
&lt;p&gt;bytes long. Adding the header size instead of subtracting it accepts a
declared length up to 2 * UBIFS_SIG_NODE_SZ larger than the node actually
holds -- past the end of c-&amp;gt;sbuf, which is vmalloc(c-&amp;gt;leb_size).
verify_pkcs7_signature() -&amp;gt; pkcs7_parse_message() -&amp;gt; asn1_ber_decoder()
is then handed that inflated length and reads beyond the allocation while
walking the DER headers. The node length comes straight from the mounted
image, so a crafted signed UBIFS image reaches this via
ubifs_read_superblock() before the signature is cryptographically checked.&lt;/p&gt;
&lt;p&gt;snod-&amp;gt;len is guaranteed to be &amp;gt;= UBIFS_SIG_NODE_SZ by the node scanner
(c-&amp;gt;ranges[UBIFS_SIG_NODE].min_len == UBIFS_SIG_NODE_SZ), so the corrected
subtraction cannot underflow. Legitimately signed images are unaffected: a
correct superblock never declares a signature longer than the node it is
embedded in.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-89720</guid>
    </item>
    <item>
      <title>GHSA-8388-259p-82vg</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8388-259p-82vg</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ubifs: fix out-of-bounds read in signature length check&lt;/p&gt;
&lt;p&gt;ubifs_sb_verify_signature() bounds the on-disk ubifs_sig_node-&amp;gt;len field
before handing the signature payload to verify_pkcs7_signature(), but the
check has the wrong sign:&lt;/p&gt;
&lt;p&gt;if (le32_to_cpu(signode-&amp;gt;len) &amp;gt; snod-&amp;gt;len + sizeof(struct ubifs_sig_node))&lt;/p&gt;
&lt;p&gt;The signature bytes start sizeof(struct ubifs_sig_node) (UBIFS_SIG_NODE_SZ,
64 bytes) into the node, so the payload is at most&lt;/p&gt;
&lt;p&gt;snod-&amp;gt;len - sizeof(struct ubifs_sig_node)&lt;/p&gt;
&lt;p&gt;bytes long. Adding the header size instead of subtracting it accepts a
declared length up to 2 * UBIFS_SIG_NODE_SZ larger than the node actually
holds -- past the end of c-&amp;gt;sbuf, which is vmalloc(c-&amp;gt;leb_size).
verify_pkcs7_signature() -&amp;gt; pkcs7_parse_message() -&amp;gt; asn1_ber_decoder()
is then handed that inflated length and reads beyond the allocation while
walking the DER headers. The node length comes straight from the mounted
image, so a crafted signed UBIFS image reaches this via
ubifs_read_superblock() before the signature is cryptographically checked.&lt;/p&gt;
&lt;p&gt;snod-&amp;gt;len is guaranteed to be &amp;gt;= UBIFS_SIG_NODE_SZ by the node scanner
(c-&amp;gt;ranges[UBIFS_SIG_NODE].min_len == UBIFS_SIG_NODE_SZ), so the corrected
subtraction cannot underflow. Legitimately signed images are unaffected: a
correct superblock never declares a signature longer than the node it is
embedded in.&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;ubifs: fix out-of-bounds read in signature length check&lt;/p&gt;
&lt;p&gt;ubifs_sb_verify_signature() bounds the on-disk ubifs_sig_node-&amp;gt;len field
before handing the signature payload to verify_pkcs7_signature(), but the
check has the wrong sign:&lt;/p&gt;
&lt;p&gt;if (le32_to_cpu(signode-&amp;gt;len) &amp;gt; snod-&amp;gt;len + sizeof(struct ubifs_sig_node))&lt;/p&gt;
&lt;p&gt;The signature bytes start sizeof(struct ubifs_sig_node) (UBIFS_SIG_NODE_SZ,
64 bytes) into the node, so the payload is at most&lt;/p&gt;
&lt;p&gt;snod-&amp;gt;len - sizeof(struct ubifs_sig_node)&lt;/p&gt;
&lt;p&gt;bytes long. Adding the header size instead of subtracting it accepts a
declared length up to 2 * UBIFS_SIG_NODE_SZ larger than the node actually
holds -- past the end of c-&amp;gt;sbuf, which is vmalloc(c-&amp;gt;leb_size).
verify_pkcs7_signature() -&amp;gt; pkcs7_parse_message() -&amp;gt; asn1_ber_decoder()
is then handed that inflated length and reads beyond the allocation while
walking the DER headers. The node length comes straight from the mounted
image, so a crafted signed UBIFS image reaches this via
ubifs_read_superblock() before the signature is cryptographically checked.&lt;/p&gt;
&lt;p&gt;snod-&amp;gt;len is guaranteed to be &amp;gt;= UBIFS_SIG_NODE_SZ by the node scanner
(c-&amp;gt;ranges[UBIFS_SIG_NODE].min_len == UBIFS_SIG_NODE_SZ), so the corrected
subtraction cannot underflow. Legitimately signed images are unaffected: a
correct superblock never declares a signature longer than the node it is
embedded in.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8388-259p-82vg</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-89720</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89720</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 219 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ubifs: fix out-of-bounds read in signature length check ubifs_sb_verify_signature() bounds the on-disk ubifs_sig_node-&amp;gt;len field before handing the signature payload to verify_pkcs7_signature(), but the check has the wrong sign: 	if (le32_to_cpu(signode-&amp;gt;len) &amp;gt; snod-&amp;gt;len + sizeof(struct ubifs_sig_node)) The signature bytes start sizeof(struct ubifs_sig_node) (UBIFS_SIG_NODE_SZ, 64 bytes) into the node, so the payload is at most 	snod-&amp;gt;len - sizeof(struct ubifs_sig_node) bytes long. Adding the header size instead of subtracting it accepts a declared length up to 2 * UBIFS_SIG_NODE_SZ larger than the node actually holds -- past the end of c-&amp;gt;sbuf, which is vmalloc(c-&amp;gt;leb_size). verify_pkcs7_signature() -&amp;gt; pkcs7_parse_message() -&amp;gt; asn1_ber_decoder() is then handed that inflated length and reads beyond the allocation while walking the DER headers. The node length comes straight from the mounted image, so a crafted signed UBIFS image reaches this via ubifs_read_superblock() before the signature is cryptographically checked. snod-&amp;gt;len is guaranteed to be &amp;gt;= UBIFS_SIG_NODE_SZ by the node scanner (c-&amp;gt;ranges[UBIFS_SIG_NODE].min_len == UBIFS_SIG_NODE_SZ), so the corrected subtraction cannot underflow. Legitimately signed images are unaffected: a correct superblock never declares a signature longer than the node it is embedded in.&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 219 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ubifs: fix out-of-bounds read in signature length check ubifs_sb_verify_signature() bounds the on-disk ubifs_sig_node-&amp;gt;len field before handing the signature payload to verify_pkcs7_signature(), but the check has the wrong sign: 	if (le32_to_cpu(signode-&amp;gt;len) &amp;gt; snod-&amp;gt;len + sizeof(struct ubifs_sig_node)) The signature bytes start sizeof(struct ubifs_sig_node) (UBIFS_SIG_NODE_SZ, 64 bytes) into the node, so the payload is at most 	snod-&amp;gt;len - sizeof(struct ubifs_sig_node) bytes long. Adding the header size instead of subtracting it accepts a declared length up to 2 * UBIFS_SIG_NODE_SZ larger than the node actually holds -- past the end of c-&amp;gt;sbuf, which is vmalloc(c-&amp;gt;leb_size). verify_pkcs7_signature() -&amp;gt; pkcs7_parse_message() -&amp;gt; asn1_ber_decoder() is then handed that inflated length and reads beyond the allocation while walking the DER headers. The node length comes straight from the mounted image, so a crafted signed UBIFS image reaches this via ubifs_read_superblock() before the signature is cryptographically checked. snod-&amp;gt;len is guaranteed to be &amp;gt;= UBIFS_SIG_NODE_SZ by the node scanner (c-&amp;gt;ranges[UBIFS_SIG_NODE].min_len == UBIFS_SIG_NODE_SZ), so the corrected subtraction cannot underflow. Legitimately signed images are unaffected: a correct superblock never declares a signature longer than the node it is embedded in.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89720</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3321 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321</guid>
    </item>
  </channel>
</rss>
