<?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-30T03:43:45.698744+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-53130</id>
    <title>CVE-2026-53130 — fs/omfs: reject s_sys_blocksize smaller than OMFS_DIR_START</title>
    <updated>2026-09-30T03:43:45.700723+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>fs/omfs: reject s_sys_blocksize smaller than OMFS_DIR_START</p>
<p>omfs_fill_super() rejects oversized s_sys_blocksize values (&gt; PAGE_SIZE),
but it does not reject values smaller than OMFS_DIR_START (0x1b8 = 440).</p>
<p>Later, omfs_make_empty() uses</p>
<p>sbi-&gt;s_sys_blocksize - OMFS_DIR_START</p>
<p>as the length argument to memset().  Since s_sys_blocksize is u32,
a crafted filesystem image with s_sys_blocksize &lt; OMFS_DIR_START causes
an unsigned underflow there, wrapping to a value near 2^32.  That drives
a ~4 GiB memset() from bh-&gt;b_data + OMFS_DIR_START and overwrites kernel
memory far beyond the backing block buffer.</p>
<p>Add the corresponding lower-bound check alongside the existing upper-bound
check in omfs_fill_super(), so that malformed images are rejected during
superblock validation before any filesystem data is processed.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-53130"/>
  </entry>
</feed>
