<?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:30:39 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99665</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99665</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/khugepaged: preserve dirty bits when collapsing PTE-mapped THPs&lt;/p&gt;
&lt;p&gt;try_collapse_pte_mapped_thp() clears PTEs without transferring their dirty
bits to the folio. A shmem read fault can map a clean folio writable, so
a later store only dirties the PTE. Losing that dirty bit allows reclaim
to discard modified data.&lt;/p&gt;
&lt;p&gt;The assumption that regular files are read-only is also obsolete since
commit 1b6444331bebb (&amp;#34;mm/khugepaged: enable clean pagecache folio collapse
for writable files&amp;#34;). In any case, transferring PTE dirty bits to the folio
when removing mappings (and while the folio is still mapped) is the right
thing to do.&lt;/p&gt;
&lt;p&gt;Use get_and_clear_ptes() to collect the dirty bits and mark the folio
dirty before unmapping it. Update the comment.&lt;/p&gt;
&lt;p&gt;This was reproduced with shmem using MADV_COLLAPSE followed by
MADV_PAGEOUT.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Chris Mason in private.&lt;/p&gt;
&lt;p&gt;[ david: adjust comment; simplify description; cover file-thp as well ]&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/khugepaged: preserve dirty bits when collapsing PTE-mapped THPs&lt;/p&gt;
&lt;p&gt;try_collapse_pte_mapped_thp() clears PTEs without transferring their dirty
bits to the folio. A shmem read fault can map a clean folio writable, so
a later store only dirties the PTE. Losing that dirty bit allows reclaim
to discard modified data.&lt;/p&gt;
&lt;p&gt;The assumption that regular files are read-only is also obsolete since
commit 1b6444331bebb (&amp;#34;mm/khugepaged: enable clean pagecache folio collapse
for writable files&amp;#34;). In any case, transferring PTE dirty bits to the folio
when removing mappings (and while the folio is still mapped) is the right
thing to do.&lt;/p&gt;
&lt;p&gt;Use get_and_clear_ptes() to collect the dirty bits and mark the folio
dirty before unmapping it. Update the comment.&lt;/p&gt;
&lt;p&gt;This was reproduced with shmem using MADV_COLLAPSE followed by
MADV_PAGEOUT.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Chris Mason in private.&lt;/p&gt;
&lt;p&gt;[ david: adjust comment; simplify description; cover file-thp as well ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99665</guid>
    </item>
    <item>
      <title>GHSA-qw5w-3h38-x8hg</title>
      <link>https://db.gcve.eu/vuln/ghsa-qw5w-3h38-x8hg</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/khugepaged: preserve dirty bits when collapsing PTE-mapped THPs&lt;/p&gt;
&lt;p&gt;try_collapse_pte_mapped_thp() clears PTEs without transferring their dirty
bits to the folio. A shmem read fault can map a clean folio writable, so
a later store only dirties the PTE. Losing that dirty bit allows reclaim
to discard modified data.&lt;/p&gt;
&lt;p&gt;The assumption that regular files are read-only is also obsolete since
commit 1b6444331bebb (&amp;#34;mm/khugepaged: enable clean pagecache folio collapse
for writable files&amp;#34;). In any case, transferring PTE dirty bits to the folio
when removing mappings (and while the folio is still mapped) is the right
thing to do.&lt;/p&gt;
&lt;p&gt;Use get_and_clear_ptes() to collect the dirty bits and mark the folio
dirty before unmapping it. Update the comment.&lt;/p&gt;
&lt;p&gt;This was reproduced with shmem using MADV_COLLAPSE followed by
MADV_PAGEOUT.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Chris Mason in private.&lt;/p&gt;
&lt;p&gt;[ david: adjust comment; simplify description; cover file-thp as well ]&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/khugepaged: preserve dirty bits when collapsing PTE-mapped THPs&lt;/p&gt;
&lt;p&gt;try_collapse_pte_mapped_thp() clears PTEs without transferring their dirty
bits to the folio. A shmem read fault can map a clean folio writable, so
a later store only dirties the PTE. Losing that dirty bit allows reclaim
to discard modified data.&lt;/p&gt;
&lt;p&gt;The assumption that regular files are read-only is also obsolete since
commit 1b6444331bebb (&amp;#34;mm/khugepaged: enable clean pagecache folio collapse
for writable files&amp;#34;). In any case, transferring PTE dirty bits to the folio
when removing mappings (and while the folio is still mapped) is the right
thing to do.&lt;/p&gt;
&lt;p&gt;Use get_and_clear_ptes() to collect the dirty bits and mark the folio
dirty before unmapping it. Update the comment.&lt;/p&gt;
&lt;p&gt;This was reproduced with shmem using MADV_COLLAPSE followed by
MADV_PAGEOUT.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Chris Mason in private.&lt;/p&gt;
&lt;p&gt;[ david: adjust comment; simplify description; cover file-thp as well ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-qw5w-3h38-x8hg</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>
