<?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:40 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99700</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99700</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/hugetlb_vmemmap: map the shared tail page writable&lt;/p&gt;
&lt;p&gt;page_ref_add_unless_zero() reads the refcount and then updates it with a
cmpxchg.  A lockless get, such as a page cache lookup or a PFN scanner,
can read a non-zero refcount from a page that is then freed and reused as
a hugetlb tail page.  If HVO remaps its struct page to the shared tail
page in between, the cmpxchg writes to read-only vmemmap:&lt;/p&gt;
&lt;p&gt;CPU0 (lockless get)               CPU1
    c = atomic_read(&amp;amp;page-&amp;gt;_refcount)
                                      page freed
                                      page allocated as a hugetlb tail
                                      HVO remaps the struct page RO
    try_cmpxchg(&amp;amp;page-&amp;gt;_refcount, &amp;amp;c, c + 1)
      -&amp;gt; write fault on read-only vmemmap&lt;/p&gt;
&lt;p&gt;The refcount is zero by then and the compare fails, but a compare-and-swap
instruction needs write access whether or not it succeeds.  The kernel
oopses when hugetlb pages are allocated at runtime with HVO enabled while
a lockless get races with it.&lt;/p&gt;
&lt;p&gt;Commit bd225530a4c7 (&amp;#34;mm/hugetlb_vmemmap: fix race with speculative PFN
walkers&amp;#34;) closed the window with RCU on both sides.  The RCU was removed
together with fake heads, on the wrong belief that it was only needed for
them.&lt;/p&gt;
&lt;p&gt;Map the shared tail page writable instead of restoring the RCU.  Every
struct page on it is a tail with a zero refcount, so a late cmpxchg
fails and leaves the page unchanged.  RCU would put r…&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/hugetlb_vmemmap: map the shared tail page writable&lt;/p&gt;
&lt;p&gt;page_ref_add_unless_zero() reads the refcount and then updates it with a
cmpxchg.  A lockless get, such as a page cache lookup or a PFN scanner,
can read a non-zero refcount from a page that is then freed and reused as
a hugetlb tail page.  If HVO remaps its struct page to the shared tail
page in between, the cmpxchg writes to read-only vmemmap:&lt;/p&gt;
&lt;p&gt;CPU0 (lockless get)               CPU1
    c = atomic_read(&amp;amp;page-&amp;gt;_refcount)
                                      page freed
                                      page allocated as a hugetlb tail
                                      HVO remaps the struct page RO
    try_cmpxchg(&amp;amp;page-&amp;gt;_refcount, &amp;amp;c, c + 1)
      -&amp;gt; write fault on read-only vmemmap&lt;/p&gt;
&lt;p&gt;The refcount is zero by then and the compare fails, but a compare-and-swap
instruction needs write access whether or not it succeeds.  The kernel
oopses when hugetlb pages are allocated at runtime with HVO enabled while
a lockless get races with it.&lt;/p&gt;
&lt;p&gt;Commit bd225530a4c7 (&amp;#34;mm/hugetlb_vmemmap: fix race with speculative PFN
walkers&amp;#34;) closed the window with RCU on both sides.  The RCU was removed
together with fake heads, on the wrong belief that it was only needed for
them.&lt;/p&gt;
&lt;p&gt;Map the shared tail page writable instead of restoring the RCU.  Every
struct page on it is a tail with a zero refcount, so a late cmpxchg
fails and leaves the page unchanged.  RCU would put r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99700</guid>
    </item>
    <item>
      <title>GHSA-7mqr-phx6-63pp</title>
      <link>https://db.gcve.eu/vuln/ghsa-7mqr-phx6-63pp</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/hugetlb_vmemmap: map the shared tail page writable&lt;/p&gt;
&lt;p&gt;page_ref_add_unless_zero() reads the refcount and then updates it with a
cmpxchg.  A lockless get, such as a page cache lookup or a PFN scanner,
can read a non-zero refcount from a page that is then freed and reused as
a hugetlb tail page.  If HVO remaps its struct page to the shared tail
page in between, the cmpxchg writes to read-only vmemmap:&lt;/p&gt;
&lt;p&gt;CPU0 (lockless get)               CPU1
    c = atomic_read(&amp;amp;page-&amp;gt;_refcount)
                                      page freed
                                      page allocated as a hugetlb tail
                                      HVO remaps the struct page RO
    try_cmpxchg(&amp;amp;page-&amp;gt;_refcount, &amp;amp;c, c + 1)
      -&amp;gt; write fault on read-only vmemmap&lt;/p&gt;
&lt;p&gt;The refcount is zero by then and the compare fails, but a compare-and-swap
instruction needs write access whether or not it succeeds.  The kernel
oopses when hugetlb pages are allocated at runtime with HVO enabled while
a lockless get races with it.&lt;/p&gt;
&lt;p&gt;Commit bd225530a4c7 (&amp;#34;mm/hugetlb_vmemmap: fix race with speculative PFN
walkers&amp;#34;) closed the window with RCU on both sides.  The RCU was removed
together with fake heads, on the wrong belief that it was only needed for
them.&lt;/p&gt;
&lt;p&gt;Map the shared tail page writable instead of restoring the RCU.  Every
struct page on it is a tail with a zero refcount, so a late cmpxchg
fails and leaves the page unchanged.  RCU would put r…&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/hugetlb_vmemmap: map the shared tail page writable&lt;/p&gt;
&lt;p&gt;page_ref_add_unless_zero() reads the refcount and then updates it with a
cmpxchg.  A lockless get, such as a page cache lookup or a PFN scanner,
can read a non-zero refcount from a page that is then freed and reused as
a hugetlb tail page.  If HVO remaps its struct page to the shared tail
page in between, the cmpxchg writes to read-only vmemmap:&lt;/p&gt;
&lt;p&gt;CPU0 (lockless get)               CPU1
    c = atomic_read(&amp;amp;page-&amp;gt;_refcount)
                                      page freed
                                      page allocated as a hugetlb tail
                                      HVO remaps the struct page RO
    try_cmpxchg(&amp;amp;page-&amp;gt;_refcount, &amp;amp;c, c + 1)
      -&amp;gt; write fault on read-only vmemmap&lt;/p&gt;
&lt;p&gt;The refcount is zero by then and the compare fails, but a compare-and-swap
instruction needs write access whether or not it succeeds.  The kernel
oopses when hugetlb pages are allocated at runtime with HVO enabled while
a lockless get races with it.&lt;/p&gt;
&lt;p&gt;Commit bd225530a4c7 (&amp;#34;mm/hugetlb_vmemmap: fix race with speculative PFN
walkers&amp;#34;) closed the window with RCU on both sides.  The RCU was removed
together with fake heads, on the wrong belief that it was only needed for
them.&lt;/p&gt;
&lt;p&gt;Map the shared tail page writable instead of restoring the RCU.  Every
struct page on it is a tail with a zero refcount, so a late cmpxchg
fails and leaves the page unchanged.  RCU would put r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-7mqr-phx6-63pp</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>
