<?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://cve.radiocsirt.org</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>Tue, 17 Nov 2026 10:11:24 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2026-99051 — CVE-2026-99051 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-99051</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-99051</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1537 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</link>
      <description>certfr-2026-avi-1537</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</guid>
    </item>
    <item>
      <title>EUVD-2026-392039</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-392039</link>
      <description>EUVD-2026-392039</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-392039</guid>
    </item>
    <item>
      <title>fkie_cve-2026-99051</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99051</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fsverity: RCU-delay the freeing of struct fsverity_info&lt;/p&gt;
&lt;p&gt;__fsverity_get_info() calls rhashtable_lookup_fast(), which just uses
rcu_read_lock() and doesn&amp;#39;t directly synchronize with
fsverity_remove_info().&lt;/p&gt;
&lt;p&gt;For the same inode this isn&amp;#39;t a problem: its fsverity_info is removed
only at inode eviction time or upon failure to enable verity, when the
inode no longer needs its fsverity_info and it will no longer be
accessed via that inode.&lt;/p&gt;
&lt;p&gt;However, this is broken and can cause a use-after-free for concurrent
__fsverity_get_info() for *different* inodes.  Those rely on following
fsverity_info::rhash_head in the rhashtable under rcu_read_lock() only.
They also use fsverity_info::inode to do the key comparison.&lt;/p&gt;
&lt;p&gt;Fix this by RCU-delaying the freeing of &amp;#39;struct fsverity_info&amp;#39; after
it&amp;#39;s been removed from the rhashtable.&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;fsverity: RCU-delay the freeing of struct fsverity_info&lt;/p&gt;
&lt;p&gt;__fsverity_get_info() calls rhashtable_lookup_fast(), which just uses
rcu_read_lock() and doesn&amp;#39;t directly synchronize with
fsverity_remove_info().&lt;/p&gt;
&lt;p&gt;For the same inode this isn&amp;#39;t a problem: its fsverity_info is removed
only at inode eviction time or upon failure to enable verity, when the
inode no longer needs its fsverity_info and it will no longer be
accessed via that inode.&lt;/p&gt;
&lt;p&gt;However, this is broken and can cause a use-after-free for concurrent
__fsverity_get_info() for *different* inodes.  Those rely on following
fsverity_info::rhash_head in the rhashtable under rcu_read_lock() only.
They also use fsverity_info::inode to do the key comparison.&lt;/p&gt;
&lt;p&gt;Fix this by RCU-delaying the freeing of &amp;#39;struct fsverity_info&amp;#39; after
it&amp;#39;s been removed from the rhashtable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-99051</guid>
    </item>
    <item>
      <title>GHSA-7hq4-c7jg-2h9h</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7hq4-c7jg-2h9h</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fsverity: RCU-delay the freeing of struct fsverity_info&lt;/p&gt;
&lt;p&gt;__fsverity_get_info() calls rhashtable_lookup_fast(), which just uses
rcu_read_lock() and doesn&amp;#39;t directly synchronize with
fsverity_remove_info().&lt;/p&gt;
&lt;p&gt;For the same inode this isn&amp;#39;t a problem: its fsverity_info is removed
only at inode eviction time or upon failure to enable verity, when the
inode no longer needs its fsverity_info and it will no longer be
accessed via that inode.&lt;/p&gt;
&lt;p&gt;However, this is broken and can cause a use-after-free for concurrent
__fsverity_get_info() for *different* inodes.  Those rely on following
fsverity_info::rhash_head in the rhashtable under rcu_read_lock() only.
They also use fsverity_info::inode to do the key comparison.&lt;/p&gt;
&lt;p&gt;Fix this by RCU-delaying the freeing of &amp;#39;struct fsverity_info&amp;#39; after
it&amp;#39;s been removed from the rhashtable.&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;fsverity: RCU-delay the freeing of struct fsverity_info&lt;/p&gt;
&lt;p&gt;__fsverity_get_info() calls rhashtable_lookup_fast(), which just uses
rcu_read_lock() and doesn&amp;#39;t directly synchronize with
fsverity_remove_info().&lt;/p&gt;
&lt;p&gt;For the same inode this isn&amp;#39;t a problem: its fsverity_info is removed
only at inode eviction time or upon failure to enable verity, when the
inode no longer needs its fsverity_info and it will no longer be
accessed via that inode.&lt;/p&gt;
&lt;p&gt;However, this is broken and can cause a use-after-free for concurrent
__fsverity_get_info() for *different* inodes.  Those rely on following
fsverity_info::rhash_head in the rhashtable under rcu_read_lock() only.
They also use fsverity_info::inode to do the key comparison.&lt;/p&gt;
&lt;p&gt;Fix this by RCU-delaying the freeing of &amp;#39;struct fsverity_info&amp;#39; after
it&amp;#39;s been removed from the rhashtable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7hq4-c7jg-2h9h</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99051</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99051</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 127 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fsverity: RCU-delay the freeing of struct fsverity_info __fsverity_get_info() calls rhashtable_lookup_fast(), which just uses rcu_read_lock() and doesn&amp;#39;t directly synchronize with fsverity_remove_info(). For the same inode this isn&amp;#39;t a problem: its fsverity_info is removed only at inode eviction time or upon failure to enable verity, when the inode no longer needs its fsverity_info and it will no longer be accessed via that inode. However, this is broken and can cause a use-after-free for concurrent __fsverity_get_info() for *different* inodes.  Those rely on following fsverity_info::rhash_head in the rhashtable under rcu_read_lock() only. They also use fsverity_info::inode to do the key comparison. Fix this by RCU-delaying the freeing of &amp;#39;struct fsverity_info&amp;#39; after it&amp;#39;s been removed from the rhashtable.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 127 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fsverity: RCU-delay the freeing of struct fsverity_info __fsverity_get_info() calls rhashtable_lookup_fast(), which just uses rcu_read_lock() and doesn&amp;#39;t directly synchronize with fsverity_remove_info(). For the same inode this isn&amp;#39;t a problem: its fsverity_info is removed only at inode eviction time or upon failure to enable verity, when the inode no longer needs its fsverity_info and it will no longer be accessed via that inode. However, this is broken and can cause a use-after-free for concurrent __fsverity_get_info() for *different* inodes.  Those rely on following fsverity_info::rhash_head in the rhashtable under rcu_read_lock() only. They also use fsverity_info::inode to do the key comparison. Fix this by RCU-delaying the freeing of &amp;#39;struct fsverity_info&amp;#39; after it&amp;#39;s been removed from the rhashtable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99051</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</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://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</guid>
    </item>
  </channel>
</rss>
