<?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-28T09:32:30.258347+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-23388</id>
    <title>CVE-2026-23388 — Squashfs: check metadata block offset is within range</title>
    <updated>2026-09-28T09:32:30.260047+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>Squashfs: check metadata block offset is within range</p>
<p>Syzkaller reports a "general protection fault in squashfs_copy_data"</p>
<p>This is ultimately caused by a corrupted index look-up table, which
produces a negative metadata block offset.</p>
<p>This is subsequently passed to squashfs_copy_data (via
squashfs_read_metadata) where the negative offset causes an out of bounds
access.</p>
<p>The fix is to check that the offset is within range in
squashfs_read_metadata.  This will trap this and other cases.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-23388"/>
  </entry>
</feed>
