<?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:04:26 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99476</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99476</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fsverity: Set S_VERITY only after rollback is no longer possible&lt;/p&gt;
&lt;p&gt;Commit f77f281b6118 (&amp;#34;fsverity: use a hashtable to find the
fsverity_info&amp;#34;) changed the implementation of FS_IOC_ENABLE_VERITY to
make concurrent reads start going through fsverity verification slightly
earlier than they did before.&lt;/p&gt;
&lt;p&gt;Instead of it happening when enable_verity() calls fsverity_set_info(),
it now happens when -&amp;gt;end_enable_verity() sets S_VERITY.&lt;/p&gt;
&lt;p&gt;However, ext4 and btrfs can roll back verity after they set S_VERITY,
causing a use-after-free.&lt;/p&gt;
&lt;p&gt;Fix that by making ext4 and btrfs set S_VERITY only after rollback is no
longer possible.  On failure, don&amp;#39;t roll back S_VERITY, but do roll back
the filesystem-specific verity flag.&lt;/p&gt;
&lt;p&gt;Also update enable_verity() to handle any future instances of this bug
more safely by warning and *not* freeing the fsverity_info.&lt;/p&gt;
&lt;p&gt;Finally, tweak some comments.  Clarify one, and move information from
another to its proper place in the comment for -&amp;gt;end_enable_verity().&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: Set S_VERITY only after rollback is no longer possible&lt;/p&gt;
&lt;p&gt;Commit f77f281b6118 (&amp;#34;fsverity: use a hashtable to find the
fsverity_info&amp;#34;) changed the implementation of FS_IOC_ENABLE_VERITY to
make concurrent reads start going through fsverity verification slightly
earlier than they did before.&lt;/p&gt;
&lt;p&gt;Instead of it happening when enable_verity() calls fsverity_set_info(),
it now happens when -&amp;gt;end_enable_verity() sets S_VERITY.&lt;/p&gt;
&lt;p&gt;However, ext4 and btrfs can roll back verity after they set S_VERITY,
causing a use-after-free.&lt;/p&gt;
&lt;p&gt;Fix that by making ext4 and btrfs set S_VERITY only after rollback is no
longer possible.  On failure, don&amp;#39;t roll back S_VERITY, but do roll back
the filesystem-specific verity flag.&lt;/p&gt;
&lt;p&gt;Also update enable_verity() to handle any future instances of this bug
more safely by warning and *not* freeing the fsverity_info.&lt;/p&gt;
&lt;p&gt;Finally, tweak some comments.  Clarify one, and move information from
another to its proper place in the comment for -&amp;gt;end_enable_verity().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99476</guid>
    </item>
    <item>
      <title>GHSA-g28v-x9c2-j5v7</title>
      <link>https://db.gcve.eu/vuln/ghsa-g28v-x9c2-j5v7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fsverity: Set S_VERITY only after rollback is no longer possible&lt;/p&gt;
&lt;p&gt;Commit f77f281b6118 (&amp;#34;fsverity: use a hashtable to find the
fsverity_info&amp;#34;) changed the implementation of FS_IOC_ENABLE_VERITY to
make concurrent reads start going through fsverity verification slightly
earlier than they did before.&lt;/p&gt;
&lt;p&gt;Instead of it happening when enable_verity() calls fsverity_set_info(),
it now happens when -&amp;gt;end_enable_verity() sets S_VERITY.&lt;/p&gt;
&lt;p&gt;However, ext4 and btrfs can roll back verity after they set S_VERITY,
causing a use-after-free.&lt;/p&gt;
&lt;p&gt;Fix that by making ext4 and btrfs set S_VERITY only after rollback is no
longer possible.  On failure, don&amp;#39;t roll back S_VERITY, but do roll back
the filesystem-specific verity flag.&lt;/p&gt;
&lt;p&gt;Also update enable_verity() to handle any future instances of this bug
more safely by warning and *not* freeing the fsverity_info.&lt;/p&gt;
&lt;p&gt;Finally, tweak some comments.  Clarify one, and move information from
another to its proper place in the comment for -&amp;gt;end_enable_verity().&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: Set S_VERITY only after rollback is no longer possible&lt;/p&gt;
&lt;p&gt;Commit f77f281b6118 (&amp;#34;fsverity: use a hashtable to find the
fsverity_info&amp;#34;) changed the implementation of FS_IOC_ENABLE_VERITY to
make concurrent reads start going through fsverity verification slightly
earlier than they did before.&lt;/p&gt;
&lt;p&gt;Instead of it happening when enable_verity() calls fsverity_set_info(),
it now happens when -&amp;gt;end_enable_verity() sets S_VERITY.&lt;/p&gt;
&lt;p&gt;However, ext4 and btrfs can roll back verity after they set S_VERITY,
causing a use-after-free.&lt;/p&gt;
&lt;p&gt;Fix that by making ext4 and btrfs set S_VERITY only after rollback is no
longer possible.  On failure, don&amp;#39;t roll back S_VERITY, but do roll back
the filesystem-specific verity flag.&lt;/p&gt;
&lt;p&gt;Also update enable_verity() to handle any future instances of this bug
more safely by warning and *not* freeing the fsverity_info.&lt;/p&gt;
&lt;p&gt;Finally, tweak some comments.  Clarify one, and move information from
another to its proper place in the comment for -&amp;gt;end_enable_verity().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-g28v-x9c2-j5v7</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>
