<?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:03:37 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99643</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99643</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;khugepaged: fix readahead lock inversion in collapse_file()&lt;/p&gt;
&lt;p&gt;collapse_file() can call page_cache_sync_readahead() while still holding
source folios locked. If truncate holds mapping-&amp;gt;invalidate_lock
exclusively and waits for one of those folios, readahead waits for
invalidate_lock and neither side can make progress.&lt;/p&gt;
&lt;p&gt;We need to release those folio locks before starting readahead. On a page
cache miss, roll back first, populate the collapse range, and retry once.
Doing readahead after rollback avoids an extra pass when all folios are
already present. If another miss occurs on retry, give up rather than keep
retrying while truncate or reclaim removes folios.&lt;/p&gt;
&lt;p&gt;Keep page_cache_sync_readahead() and wait for read I/O with
filemap_lock_folio(), releasing each folio before moving to the next. The
existing uptodate check during collapse still handles read errors.&lt;/p&gt;
&lt;p&gt;Shmem uses shmem_get_folio() for swapin and fallocated folios without
taking mapping-&amp;gt;invalidate_lock, so it is unaffected.&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;khugepaged: fix readahead lock inversion in collapse_file()&lt;/p&gt;
&lt;p&gt;collapse_file() can call page_cache_sync_readahead() while still holding
source folios locked. If truncate holds mapping-&amp;gt;invalidate_lock
exclusively and waits for one of those folios, readahead waits for
invalidate_lock and neither side can make progress.&lt;/p&gt;
&lt;p&gt;We need to release those folio locks before starting readahead. On a page
cache miss, roll back first, populate the collapse range, and retry once.
Doing readahead after rollback avoids an extra pass when all folios are
already present. If another miss occurs on retry, give up rather than keep
retrying while truncate or reclaim removes folios.&lt;/p&gt;
&lt;p&gt;Keep page_cache_sync_readahead() and wait for read I/O with
filemap_lock_folio(), releasing each folio before moving to the next. The
existing uptodate check during collapse still handles read errors.&lt;/p&gt;
&lt;p&gt;Shmem uses shmem_get_folio() for swapin and fallocated folios without
taking mapping-&amp;gt;invalidate_lock, so it is unaffected.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99643</guid>
    </item>
    <item>
      <title>GHSA-cq67-v8mm-j2c8</title>
      <link>https://db.gcve.eu/vuln/ghsa-cq67-v8mm-j2c8</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;khugepaged: fix readahead lock inversion in collapse_file()&lt;/p&gt;
&lt;p&gt;collapse_file() can call page_cache_sync_readahead() while still holding
source folios locked. If truncate holds mapping-&amp;gt;invalidate_lock
exclusively and waits for one of those folios, readahead waits for
invalidate_lock and neither side can make progress.&lt;/p&gt;
&lt;p&gt;We need to release those folio locks before starting readahead. On a page
cache miss, roll back first, populate the collapse range, and retry once.
Doing readahead after rollback avoids an extra pass when all folios are
already present. If another miss occurs on retry, give up rather than keep
retrying while truncate or reclaim removes folios.&lt;/p&gt;
&lt;p&gt;Keep page_cache_sync_readahead() and wait for read I/O with
filemap_lock_folio(), releasing each folio before moving to the next. The
existing uptodate check during collapse still handles read errors.&lt;/p&gt;
&lt;p&gt;Shmem uses shmem_get_folio() for swapin and fallocated folios without
taking mapping-&amp;gt;invalidate_lock, so it is unaffected.&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;khugepaged: fix readahead lock inversion in collapse_file()&lt;/p&gt;
&lt;p&gt;collapse_file() can call page_cache_sync_readahead() while still holding
source folios locked. If truncate holds mapping-&amp;gt;invalidate_lock
exclusively and waits for one of those folios, readahead waits for
invalidate_lock and neither side can make progress.&lt;/p&gt;
&lt;p&gt;We need to release those folio locks before starting readahead. On a page
cache miss, roll back first, populate the collapse range, and retry once.
Doing readahead after rollback avoids an extra pass when all folios are
already present. If another miss occurs on retry, give up rather than keep
retrying while truncate or reclaim removes folios.&lt;/p&gt;
&lt;p&gt;Keep page_cache_sync_readahead() and wait for read I/O with
filemap_lock_folio(), releasing each folio before moving to the next. The
existing uptodate check during collapse still handles read errors.&lt;/p&gt;
&lt;p&gt;Shmem uses shmem_get_folio() for swapin and fallocated folios without
taking mapping-&amp;gt;invalidate_lock, so it is unaffected.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-cq67-v8mm-j2c8</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>
