<?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:30:39.361471+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-99732</id>
    <title>fkie_cve-2026-99732</title>
    <updated>2026-11-20T21:30:39.364324+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>mm/filemap: read mapping-&gt;a_ops-&gt;free_folio under i_lock</p>
<p>memory_failure() -&gt; ... -&gt; filemap_remove_folio() can read mapping-&gt;a_ops
after the inode has been freed. Once the folio is deleted from the
pagecache it no longer pins the mapping, so after i_lock is dropped
e.g., a concurrent final iput() can evict and free the inode before
filemap_free_folio() looks up mapping-&gt;a_ops-&gt;free_folio.</p>
<p>Most callers hold a reference on the inode, but not all.</p>
<p>Documentation/filesystems/vfs.rst explicitly states that -&gt;free_folio()
must not assume the original address_space mapping still exists.</p>
<p>Fix it by loading -&gt;free_folio while i_lock is still held, similar to
what folio_unmap_invalidate() does.</p>
<p>Inline filemap_free_folio() into its remaining caller such that
delete_from_page_cache_batch() also just loads the callback before
dropping the i_lock.</p>
<p>The bug was found by code inspection and has not been reproduced.</p>
<p>Fix generated by an LLM and sent by Josef Bacik in private.</p>
<p>[ david: get rid of filemap_free_folio() entirely; improve patch description ]</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-99732"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-5qgv-47p9-j8px</id>
    <title>GHSA-5qgv-47p9-j8px</title>
    <updated>2026-11-20T21:30:39.364413+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>mm/filemap: read mapping-&gt;a_ops-&gt;free_folio under i_lock</p>
<p>memory_failure() -&gt; ... -&gt; filemap_remove_folio() can read mapping-&gt;a_ops
after the inode has been freed. Once the folio is deleted from the
pagecache it no longer pins the mapping, so after i_lock is dropped
e.g., a concurrent final iput() can evict and free the inode before
filemap_free_folio() looks up mapping-&gt;a_ops-&gt;free_folio.</p>
<p>Most callers hold a reference on the inode, but not all.</p>
<p>Documentation/filesystems/vfs.rst explicitly states that -&gt;free_folio()
must not assume the original address_space mapping still exists.</p>
<p>Fix it by loading -&gt;free_folio while i_lock is still held, similar to
what folio_unmap_invalidate() does.</p>
<p>Inline filemap_free_folio() into its remaining caller such that
delete_from_page_cache_batch() also just loads the callback before
dropping the i_lock.</p>
<p>The bug was found by code inspection and has not been reproduced.</p>
<p>Fix generated by an LLM and sent by Josef Bacik in private.</p>
<p>[ david: get rid of filemap_free_folio() entirely; improve patch description ]</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-5qgv-47p9-j8px"/>
  </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:30:39.364455+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>
