<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 20 Nov 2026 21:27:33 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99422</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99422</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ovl: use the pinned upper dir in ovl_fix_origin()&lt;/p&gt;
&lt;p&gt;Renames made directly on the upper filesystem during a lookup crash the
kernel.&lt;/p&gt;
&lt;p&gt;A dentry that is passed to vfs_setxattr() must be pinned.
ovl_fix_origin() passes upper-&amp;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.&lt;/p&gt;
&lt;p&gt;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().&lt;/p&gt;
&lt;p&gt;Fix this by passing the upper dentry that the overlay parent holds.&lt;/p&gt;
&lt;p&gt;[amir: add helper ovl_set_impure_dir()]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ovl: use the pinned upper dir in ovl_fix_origin()&lt;/p&gt;
&lt;p&gt;Renames made directly on the upper filesystem during a lookup crash the
kernel.&lt;/p&gt;
&lt;p&gt;A dentry that is passed to vfs_setxattr() must be pinned.
ovl_fix_origin() passes upper-&amp;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.&lt;/p&gt;
&lt;p&gt;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().&lt;/p&gt;
&lt;p&gt;Fix this by passing the upper dentry that the overlay parent holds.&lt;/p&gt;
&lt;p&gt;[amir: add helper ovl_set_impure_dir()]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99422</guid>
    </item>
    <item>
      <title>GHSA-v4c4-7j95-qcj8</title>
      <link>https://db.gcve.eu/vuln/ghsa-v4c4-7j95-qcj8</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ovl: use the pinned upper dir in ovl_fix_origin()&lt;/p&gt;
&lt;p&gt;Renames made directly on the upper filesystem during a lookup crash the
kernel.&lt;/p&gt;
&lt;p&gt;A dentry that is passed to vfs_setxattr() must be pinned.
ovl_fix_origin() passes upper-&amp;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.&lt;/p&gt;
&lt;p&gt;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().&lt;/p&gt;
&lt;p&gt;Fix this by passing the upper dentry that the overlay parent holds.&lt;/p&gt;
&lt;p&gt;[amir: add helper ovl_set_impure_dir()]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ovl: use the pinned upper dir in ovl_fix_origin()&lt;/p&gt;
&lt;p&gt;Renames made directly on the upper filesystem during a lookup crash the
kernel.&lt;/p&gt;
&lt;p&gt;A dentry that is passed to vfs_setxattr() must be pinned.
ovl_fix_origin() passes upper-&amp;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.&lt;/p&gt;
&lt;p&gt;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().&lt;/p&gt;
&lt;p&gt;Fix this by passing the upper dentry that the overlay parent holds.&lt;/p&gt;
&lt;p&gt;[amir: add helper ovl_set_impure_dir()]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-v4c4-7j95-qcj8</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4695</guid>
    </item>
  </channel>
</rss>
