<?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-29T01:58:58.754341+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-93258</id>
    <title>CVE-2026-93258 — ocfs2: do not use make_bad_inode() in ocfs2_read_inode_block_full()</title>
    <updated>2026-09-29T01:58:58.757379+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>ocfs2: do not use make_bad_inode() in ocfs2_read_inode_block_full()</p>
<p>This reverts commit 58b6fcd2ab34 ("ocfs2: mark inode bad upon validation
failure during read").</p>
<p>Since 'make_bad_inode()' resets inode type to S_IFREG, doing this for
directory inode during active VFS lookup is likely to confuse the latter,
including VFS_BUG_ON_INODE() triggered in this case.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-93258"/>
  </entry>
</feed>
