<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-20T21:04:24.900120+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-99476</id>
    <title>fkie_cve-2026-99476</title>
    <updated>2026-11-20T21:04:24.906159+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>fsverity: Set S_VERITY only after rollback is no longer possible</p>
<p>Commit f77f281b6118 ("fsverity: use a hashtable to find the
fsverity_info") changed the implementation of FS_IOC_ENABLE_VERITY to
make concurrent reads start going through fsverity verification slightly
earlier than they did before.</p>
<p>Instead of it happening when enable_verity() calls fsverity_set_info(),
it now happens when -&gt;end_enable_verity() sets S_VERITY.</p>
<p>However, ext4 and btrfs can roll back verity after they set S_VERITY,
causing a use-after-free.</p>
<p>Fix that by making ext4 and btrfs set S_VERITY only after rollback is no
longer possible.  On failure, don't roll back S_VERITY, but do roll back
the filesystem-specific verity flag.</p>
<p>Also update enable_verity() to handle any future instances of this bug
more safely by warning and *not* freeing the fsverity_info.</p>
<p>Finally, tweak some comments.  Clarify one, and move information from
another to its proper place in the comment for -&gt;end_enable_verity().</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-99476"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-g28v-x9c2-j5v7</id>
    <title>GHSA-g28v-x9c2-j5v7</title>
    <updated>2026-11-20T21:04:24.906341+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>fsverity: Set S_VERITY only after rollback is no longer possible</p>
<p>Commit f77f281b6118 ("fsverity: use a hashtable to find the
fsverity_info") changed the implementation of FS_IOC_ENABLE_VERITY to
make concurrent reads start going through fsverity verification slightly
earlier than they did before.</p>
<p>Instead of it happening when enable_verity() calls fsverity_set_info(),
it now happens when -&gt;end_enable_verity() sets S_VERITY.</p>
<p>However, ext4 and btrfs can roll back verity after they set S_VERITY,
causing a use-after-free.</p>
<p>Fix that by making ext4 and btrfs set S_VERITY only after rollback is no
longer possible.  On failure, don't roll back S_VERITY, but do roll back
the filesystem-specific verity flag.</p>
<p>Also update enable_verity() to handle any future instances of this bug
more safely by warning and *not* freeing the fsverity_info.</p>
<p>Finally, tweak some comments.  Clarify one, and move information from
another to its proper place in the comment for -&gt;end_enable_verity().</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-g28v-x9c2-j5v7"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</id>
    <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
    <updated>2026-11-20T21:04:24.906388+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/wid-sec-w-2026-4695"/>
  </entry>
</feed>
