<?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://vulnerability.circl.lu</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>Mon, 28 Sep 2026 15:18:50 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-97950</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-97950</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;configfs: pin the symlink target&amp;#39;s dirent instead of chasing -&amp;gt;ci_dentry&lt;/p&gt;
&lt;p&gt;create_link() reads the target&amp;#39;s configfs_dirent from
item-&amp;gt;ci_dentry-&amp;gt;d_fsdata, relying on the item reference taken by
get_target().  That reference pins the item, not its dentry: the dentry is
pinned by DCACHE_PERSISTENT, which configfs_remove_dir() releases via
simple_rmdir() while the item is still alive.  A symlink racing with rmdir
of its target can therefore find -&amp;gt;ci_dentry freed and its dirent
released, triggering WARN_ON(!atomic_read(&amp;amp;sd-&amp;gt;s_count)) in configfs_get().&lt;/p&gt;
&lt;p&gt;Take the dirent in get_target() as well, under -&amp;gt;d_lock and atomically
with the item reference, and pass it down to create_link().  A hashed
dentry has not been killed yet, so its -&amp;gt;d_fsdata reference keeps the
dirent alive there.&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;configfs: pin the symlink target&amp;#39;s dirent instead of chasing -&amp;gt;ci_dentry&lt;/p&gt;
&lt;p&gt;create_link() reads the target&amp;#39;s configfs_dirent from
item-&amp;gt;ci_dentry-&amp;gt;d_fsdata, relying on the item reference taken by
get_target().  That reference pins the item, not its dentry: the dentry is
pinned by DCACHE_PERSISTENT, which configfs_remove_dir() releases via
simple_rmdir() while the item is still alive.  A symlink racing with rmdir
of its target can therefore find -&amp;gt;ci_dentry freed and its dirent
released, triggering WARN_ON(!atomic_read(&amp;amp;sd-&amp;gt;s_count)) in configfs_get().&lt;/p&gt;
&lt;p&gt;Take the dirent in get_target() as well, under -&amp;gt;d_lock and atomically
with the item reference, and pass it down to create_link().  A hashed
dentry has not been killed yet, so its -&amp;gt;d_fsdata reference keeps the
dirent alive there.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-97950</guid>
    </item>
    <item>
      <title>GHSA-6xvc-m8wh-p8q8</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-6xvc-m8wh-p8q8</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;configfs: pin the symlink target&amp;#39;s dirent instead of chasing -&amp;gt;ci_dentry&lt;/p&gt;
&lt;p&gt;create_link() reads the target&amp;#39;s configfs_dirent from
item-&amp;gt;ci_dentry-&amp;gt;d_fsdata, relying on the item reference taken by
get_target().  That reference pins the item, not its dentry: the dentry is
pinned by DCACHE_PERSISTENT, which configfs_remove_dir() releases via
simple_rmdir() while the item is still alive.  A symlink racing with rmdir
of its target can therefore find -&amp;gt;ci_dentry freed and its dirent
released, triggering WARN_ON(!atomic_read(&amp;amp;sd-&amp;gt;s_count)) in configfs_get().&lt;/p&gt;
&lt;p&gt;Take the dirent in get_target() as well, under -&amp;gt;d_lock and atomically
with the item reference, and pass it down to create_link().  A hashed
dentry has not been killed yet, so its -&amp;gt;d_fsdata reference keeps the
dirent alive there.&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;configfs: pin the symlink target&amp;#39;s dirent instead of chasing -&amp;gt;ci_dentry&lt;/p&gt;
&lt;p&gt;create_link() reads the target&amp;#39;s configfs_dirent from
item-&amp;gt;ci_dentry-&amp;gt;d_fsdata, relying on the item reference taken by
get_target().  That reference pins the item, not its dentry: the dentry is
pinned by DCACHE_PERSISTENT, which configfs_remove_dir() releases via
simple_rmdir() while the item is still alive.  A symlink racing with rmdir
of its target can therefore find -&amp;gt;ci_dentry freed and its dirent
released, triggering WARN_ON(!atomic_read(&amp;amp;sd-&amp;gt;s_count)) in configfs_get().&lt;/p&gt;
&lt;p&gt;Take the dirent in get_target() as well, under -&amp;gt;d_lock and atomically
with the item reference, and pass it down to create_link().  A hashed
dentry has not been killed yet, so its -&amp;gt;d_fsdata reference keeps the
dirent alive there.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-6xvc-m8wh-p8q8</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-97950</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-97950</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: configfs: pin the symlink target&amp;#39;s dirent instead of chasing -&amp;gt;ci_dentry create_link() reads the target&amp;#39;s configfs_dirent from item-&amp;gt;ci_dentry-&amp;gt;d_fsdata, relying on the item reference taken by get_target().  That reference pins the item, not its dentry: the dentry is pinned by DCACHE_PERSISTENT, which configfs_remove_dir() releases via simple_rmdir() while the item is still alive.  A symlink racing with rmdir of its target can therefore find -&amp;gt;ci_dentry freed and its dirent released, triggering WARN_ON(!atomic_read(&amp;amp;sd-&amp;gt;s_count)) in configfs_get(). Take the dirent in get_target() as well, under -&amp;gt;d_lock and atomically with the item reference, and pass it down to create_link().  A hashed dentry has not been killed yet, so its -&amp;gt;d_fsdata reference keeps the dirent alive there.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: configfs: pin the symlink target&amp;#39;s dirent instead of chasing -&amp;gt;ci_dentry create_link() reads the target&amp;#39;s configfs_dirent from item-&amp;gt;ci_dentry-&amp;gt;d_fsdata, relying on the item reference taken by get_target().  That reference pins the item, not its dentry: the dentry is pinned by DCACHE_PERSISTENT, which configfs_remove_dir() releases via simple_rmdir() while the item is still alive.  A symlink racing with rmdir of its target can therefore find -&amp;gt;ci_dentry freed and its dirent released, triggering WARN_ON(!atomic_read(&amp;amp;sd-&amp;gt;s_count)) in configfs_get(). Take the dirent in get_target() as well, under -&amp;gt;d_lock and atomically with the item reference, and pass it down to create_link().  A hashed dentry has not been killed yet, so its -&amp;gt;d_fsdata reference keeps the dirent alive there.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-97950</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3579 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</guid>
    </item>
  </channel>
</rss>
