<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T03:05:42.185340+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-89720</id>
    <title>CVE-2026-89720 — ubifs: fix out-of-bounds read in signature length check</title>
    <updated>2026-09-29T03:05:42.389570+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ubifs: fix out-of-bounds read in signature length check</p>
<p>ubifs_sb_verify_signature() bounds the on-disk ubifs_sig_node-&gt;len field
before handing the signature payload to verify_pkcs7_signature(), but the
check has the wrong sign:</p>
<p>if (le32_to_cpu(signode-&gt;len) &gt; snod-&gt;len + sizeof(struct ubifs_sig_node))</p>
<p>The signature bytes start sizeof(struct ubifs_sig_node) (UBIFS_SIG_NODE_SZ,
64 bytes) into the node, so the payload is at most</p>
<p>snod-&gt;len - sizeof(struct ubifs_sig_node)</p>
<p>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-&gt;sbuf, which is vmalloc(c-&gt;leb_size).
verify_pkcs7_signature() -&gt; pkcs7_parse_message() -&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.</p>
<p>snod-&gt;len is guaranteed to be &gt;= UBIFS_SIG_NODE_SZ by the node scanner
(c-&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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-89720"/>
  </entry>
</feed>
