<?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-29T21:27:52.804263+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-2023-53222</id>
    <title>CVE-2023-53222 — jfs: jfs_dmap: Validate db_l2nbperpage while mounting</title>
    <updated>2026-09-29T21:27:52.805886+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>jfs: jfs_dmap: Validate db_l2nbperpage while mounting</p>
<p>In jfs_dmap.c at line 381, BLKTODMAP is used to get a logical block
number inside dbFree(). db_l2nbperpage, which is the log2 number of
blocks per page, is passed as an argument to BLKTODMAP which uses it
for shifting.</p>
<p>Syzbot reported a shift out-of-bounds crash because db_l2nbperpage is
too big. This happens because the large value is set without any
validation in dbMount() at line 181.</p>
<p>Thus, make sure that db_l2nbperpage is correct while mounting.</p>
<p>Max number of blocks per page = Page size / Min block size
=&gt; log2(Max num_block per page) = log2(Page size / Min block size)
				= log2(Page size) - log2(Min block size)</p>
<p>=&gt; Max db_l2nbperpage = L2PSIZE - L2MINBLOCKSIZE</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2023-53222"/>
  </entry>
</feed>
