<?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:31 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99462</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99462</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/truncate: look up the end-edge straddler by index&lt;/p&gt;
&lt;p&gt;In truncate_inode_partial_folio(), after the first split at the start
edge, folio_split() unlocks and drops the refcount of the after-split
sub-folios.  The sub-folio straddling the end of the truncation range is
therefore unlocked and only transiently ref&amp;#39;d in the page cache while the
code still derives it from a page pointer inside the original folio.&lt;/p&gt;
&lt;p&gt;Between the first split finishing and page_folio() resolving split_at2,
that tail page can be reclaimed, freed and reallocated as a new large
folio in the same mapping at a different file offset.  folio2 then points
at a folio that does not cover the end boundary, yet folio2-&amp;gt;mapping ==
folio-&amp;gt;mapping still holds, so the stale pointer passes the mapping check
and folio_split_or_unmap() splits a folio at a wrong position (or, with a
transient refcount, a use-after-free window opens between try_get and the
split).  __folio_split()&amp;#39;s own folio != page_folio(split_at) check cannot
catch this either since split_at2 has been reallocated as part of the new
folio, so page_folio(split_at2) resolves back to folio2.&lt;/p&gt;
&lt;p&gt;Look the straddler up by its page index instead.  __filemap_get_folio()
returns the folio currently covering the boundary, ref&amp;#39;d and locked, with
the mapping validated under the lock, so the split target is always the
real folio at the end edge.&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;mm/truncate: look up the end-edge straddler by index&lt;/p&gt;
&lt;p&gt;In truncate_inode_partial_folio(), after the first split at the start
edge, folio_split() unlocks and drops the refcount of the after-split
sub-folios.  The sub-folio straddling the end of the truncation range is
therefore unlocked and only transiently ref&amp;#39;d in the page cache while the
code still derives it from a page pointer inside the original folio.&lt;/p&gt;
&lt;p&gt;Between the first split finishing and page_folio() resolving split_at2,
that tail page can be reclaimed, freed and reallocated as a new large
folio in the same mapping at a different file offset.  folio2 then points
at a folio that does not cover the end boundary, yet folio2-&amp;gt;mapping ==
folio-&amp;gt;mapping still holds, so the stale pointer passes the mapping check
and folio_split_or_unmap() splits a folio at a wrong position (or, with a
transient refcount, a use-after-free window opens between try_get and the
split).  __folio_split()&amp;#39;s own folio != page_folio(split_at) check cannot
catch this either since split_at2 has been reallocated as part of the new
folio, so page_folio(split_at2) resolves back to folio2.&lt;/p&gt;
&lt;p&gt;Look the straddler up by its page index instead.  __filemap_get_folio()
returns the folio currently covering the boundary, ref&amp;#39;d and locked, with
the mapping validated under the lock, so the split target is always the
real folio at the end edge.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99462</guid>
    </item>
    <item>
      <title>GHSA-j63m-mh54-g9wg</title>
      <link>https://db.gcve.eu/vuln/ghsa-j63m-mh54-g9wg</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/truncate: look up the end-edge straddler by index&lt;/p&gt;
&lt;p&gt;In truncate_inode_partial_folio(), after the first split at the start
edge, folio_split() unlocks and drops the refcount of the after-split
sub-folios.  The sub-folio straddling the end of the truncation range is
therefore unlocked and only transiently ref&amp;#39;d in the page cache while the
code still derives it from a page pointer inside the original folio.&lt;/p&gt;
&lt;p&gt;Between the first split finishing and page_folio() resolving split_at2,
that tail page can be reclaimed, freed and reallocated as a new large
folio in the same mapping at a different file offset.  folio2 then points
at a folio that does not cover the end boundary, yet folio2-&amp;gt;mapping ==
folio-&amp;gt;mapping still holds, so the stale pointer passes the mapping check
and folio_split_or_unmap() splits a folio at a wrong position (or, with a
transient refcount, a use-after-free window opens between try_get and the
split).  __folio_split()&amp;#39;s own folio != page_folio(split_at) check cannot
catch this either since split_at2 has been reallocated as part of the new
folio, so page_folio(split_at2) resolves back to folio2.&lt;/p&gt;
&lt;p&gt;Look the straddler up by its page index instead.  __filemap_get_folio()
returns the folio currently covering the boundary, ref&amp;#39;d and locked, with
the mapping validated under the lock, so the split target is always the
real folio at the end edge.&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;mm/truncate: look up the end-edge straddler by index&lt;/p&gt;
&lt;p&gt;In truncate_inode_partial_folio(), after the first split at the start
edge, folio_split() unlocks and drops the refcount of the after-split
sub-folios.  The sub-folio straddling the end of the truncation range is
therefore unlocked and only transiently ref&amp;#39;d in the page cache while the
code still derives it from a page pointer inside the original folio.&lt;/p&gt;
&lt;p&gt;Between the first split finishing and page_folio() resolving split_at2,
that tail page can be reclaimed, freed and reallocated as a new large
folio in the same mapping at a different file offset.  folio2 then points
at a folio that does not cover the end boundary, yet folio2-&amp;gt;mapping ==
folio-&amp;gt;mapping still holds, so the stale pointer passes the mapping check
and folio_split_or_unmap() splits a folio at a wrong position (or, with a
transient refcount, a use-after-free window opens between try_get and the
split).  __folio_split()&amp;#39;s own folio != page_folio(split_at) check cannot
catch this either since split_at2 has been reallocated as part of the new
folio, so page_folio(split_at2) resolves back to folio2.&lt;/p&gt;
&lt;p&gt;Look the straddler up by its page index instead.  __filemap_get_folio()
returns the folio currently covering the boundary, ref&amp;#39;d and locked, with
the mapping validated under the lock, so the split target is always the
real folio at the end edge.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-j63m-mh54-g9wg</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99462 — mm/truncate: look up the end-edge straddler by index</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-99462</link>
      <description>msrc_CVE-2026-99462</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-99462</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>
