<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-20T21:22:13.154014+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-99422</id>
    <title>CVE-2026-99422 — ovl: use the pinned upper dir in ovl_fix_origin()</title>
    <updated>2026-11-20T21:22:13.155827+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>ovl: use the pinned upper dir in ovl_fix_origin()</p>
<p>Renames made directly on the upper filesystem during a lookup crash the
kernel.</p>
<p>A dentry that is passed to vfs_setxattr() must be pinned.
ovl_fix_origin() passes upper-&gt;d_parent to ovl_set_impure() without a
reference, and the lookup holds no lock of the upper directory. A
rename on the upper filesystem changes d_parent, and only the child
pins the new parent, so a second rename and an rmdir free it.</p>
<p>With delays in ovl_fix_origin() and ovl_set_impure(), renaming the upper
directory twice and removing the intermediate parent during the lookup
of a merge directory without an origin xattr gave a KASAN
use-after-free in vfs_setxattr().</p>
<p>Fix this by passing the upper dentry that the overlay parent holds.</p>
<p>[amir: add helper ovl_set_impure_dir()]</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-99422"/>
  </entry>
</feed>
