<?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:42 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99514</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99514</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;landlock: Fix superblock use-after-free in release_inode()&lt;/p&gt;
&lt;p&gt;Without this fix, release_inode() (task 1) can race with a umount
operation in hook_sb_delete() (task 2).  The order of operations in
which the race occurs is:&lt;/p&gt;
&lt;p&gt;* task 2: hook_sb_delete() arrives at the end of the function, waiting
  for landlock_superblock(sb)-&amp;gt;inode_refs to become zero.
* task 1: release_inode(): does atomic_long_dec_and_test(), decrementing
  inode_refs to zero.
* task 2: gets woken up through some other means, sees that inode_refs
  is zero and returns.  The caller is the unmount operation and proceeds
  to release the superblock.
* task 1: Runs wake_up_var(&amp;amp;landlock_superblock(sb)-&amp;gt;inode_refs),
  *dereferencing the sb_security on the freed-up superblock*.&lt;/p&gt;
&lt;p&gt;Notably, wake_up_var() does not dereference the pointer passed to it,
and only uses it to determine an overapproximated set of tasks to wake
up. So while it&amp;#39;s potentially possible for an attacker to provide a
different value for that pointer, this only results in the wrong set of
tasks getting woken up, and in this scenario, no further tasks are
actually waiting.&lt;/p&gt;
&lt;p&gt;Nevertheless, KASAN detects it as a slab-use-after-free read on
sb-&amp;gt;s_security:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in release_inode+0x196/0x290
  Read of size 8 at addr ffff888103b6c0a8 by task repro/217
   release_inode+0x196/0x290
   landlock_put_object+0x71/0x90
   landlock_free_rules+0x38/0xc0
   landlock_put_r…&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;landlock: Fix superblock use-after-free in release_inode()&lt;/p&gt;
&lt;p&gt;Without this fix, release_inode() (task 1) can race with a umount
operation in hook_sb_delete() (task 2).  The order of operations in
which the race occurs is:&lt;/p&gt;
&lt;p&gt;* task 2: hook_sb_delete() arrives at the end of the function, waiting
  for landlock_superblock(sb)-&amp;gt;inode_refs to become zero.
* task 1: release_inode(): does atomic_long_dec_and_test(), decrementing
  inode_refs to zero.
* task 2: gets woken up through some other means, sees that inode_refs
  is zero and returns.  The caller is the unmount operation and proceeds
  to release the superblock.
* task 1: Runs wake_up_var(&amp;amp;landlock_superblock(sb)-&amp;gt;inode_refs),
  *dereferencing the sb_security on the freed-up superblock*.&lt;/p&gt;
&lt;p&gt;Notably, wake_up_var() does not dereference the pointer passed to it,
and only uses it to determine an overapproximated set of tasks to wake
up. So while it&amp;#39;s potentially possible for an attacker to provide a
different value for that pointer, this only results in the wrong set of
tasks getting woken up, and in this scenario, no further tasks are
actually waiting.&lt;/p&gt;
&lt;p&gt;Nevertheless, KASAN detects it as a slab-use-after-free read on
sb-&amp;gt;s_security:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in release_inode+0x196/0x290
  Read of size 8 at addr ffff888103b6c0a8 by task repro/217
   release_inode+0x196/0x290
   landlock_put_object+0x71/0x90
   landlock_free_rules+0x38/0xc0
   landlock_put_r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99514</guid>
    </item>
    <item>
      <title>GHSA-hj8q-29c2-x354</title>
      <link>https://db.gcve.eu/vuln/ghsa-hj8q-29c2-x354</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;landlock: Fix superblock use-after-free in release_inode()&lt;/p&gt;
&lt;p&gt;Without this fix, release_inode() (task 1) can race with a umount
operation in hook_sb_delete() (task 2).  The order of operations in
which the race occurs is:&lt;/p&gt;
&lt;p&gt;* task 2: hook_sb_delete() arrives at the end of the function, waiting
  for landlock_superblock(sb)-&amp;gt;inode_refs to become zero.
* task 1: release_inode(): does atomic_long_dec_and_test(), decrementing
  inode_refs to zero.
* task 2: gets woken up through some other means, sees that inode_refs
  is zero and returns.  The caller is the unmount operation and proceeds
  to release the superblock.
* task 1: Runs wake_up_var(&amp;amp;landlock_superblock(sb)-&amp;gt;inode_refs),
  *dereferencing the sb_security on the freed-up superblock*.&lt;/p&gt;
&lt;p&gt;Notably, wake_up_var() does not dereference the pointer passed to it,
and only uses it to determine an overapproximated set of tasks to wake
up. So while it&amp;#39;s potentially possible for an attacker to provide a
different value for that pointer, this only results in the wrong set of
tasks getting woken up, and in this scenario, no further tasks are
actually waiting.&lt;/p&gt;
&lt;p&gt;Nevertheless, KASAN detects it as a slab-use-after-free read on
sb-&amp;gt;s_security:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in release_inode+0x196/0x290
  Read of size 8 at addr ffff888103b6c0a8 by task repro/217
   release_inode+0x196/0x290
   landlock_put_object+0x71/0x90
   landlock_free_rules+0x38/0xc0
   landlock_put_r…&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;landlock: Fix superblock use-after-free in release_inode()&lt;/p&gt;
&lt;p&gt;Without this fix, release_inode() (task 1) can race with a umount
operation in hook_sb_delete() (task 2).  The order of operations in
which the race occurs is:&lt;/p&gt;
&lt;p&gt;* task 2: hook_sb_delete() arrives at the end of the function, waiting
  for landlock_superblock(sb)-&amp;gt;inode_refs to become zero.
* task 1: release_inode(): does atomic_long_dec_and_test(), decrementing
  inode_refs to zero.
* task 2: gets woken up through some other means, sees that inode_refs
  is zero and returns.  The caller is the unmount operation and proceeds
  to release the superblock.
* task 1: Runs wake_up_var(&amp;amp;landlock_superblock(sb)-&amp;gt;inode_refs),
  *dereferencing the sb_security on the freed-up superblock*.&lt;/p&gt;
&lt;p&gt;Notably, wake_up_var() does not dereference the pointer passed to it,
and only uses it to determine an overapproximated set of tasks to wake
up. So while it&amp;#39;s potentially possible for an attacker to provide a
different value for that pointer, this only results in the wrong set of
tasks getting woken up, and in this scenario, no further tasks are
actually waiting.&lt;/p&gt;
&lt;p&gt;Nevertheless, KASAN detects it as a slab-use-after-free read on
sb-&amp;gt;s_security:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in release_inode+0x196/0x290
  Read of size 8 at addr ffff888103b6c0a8 by task repro/217
   release_inode+0x196/0x290
   landlock_put_object+0x71/0x90
   landlock_free_rules+0x38/0xc0
   landlock_put_r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-hj8q-29c2-x354</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>
