<?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-99728</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99728</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/huge_memory: fix list corruption when deferred_split_scan() races with deferred_split_folio()&lt;/p&gt;
&lt;p&gt;Since the deferred split queue became a list_lru, the isolate callback
moves the folios it took a reference on to an on-stack list, linked
through folio-&amp;gt;_deferred_list, and deferred_split_scan() takes them off
that list with list_del_init() without holding the list_lru lock.&lt;/p&gt;
&lt;p&gt;deferred_split_folio() does not know about the on-stack list. It only
holds the list_lru lock when it looks at the same list_head, and it can
run for such a folio: a THP is queued when it is mapped, as a candidate
for the underused check, and is queued &amp;#34;again&amp;#34; when a part of it gets
unmapped:&lt;/p&gt;
&lt;p&gt;CPU0 deferred_split_scan()          CPU1 deferred_split_folio()
  list_del_init(&amp;amp;folio-&amp;gt;_deferred_list)
    next-&amp;gt;prev = prev
    prev-&amp;gt;next = next
    entry-&amp;gt;next = entry
                                      list_lru_lock_irqsave()
                                      folio_set_partially_mapped()
                                      __list_lru_add()
                                        list_empty(item)  -&amp;gt; true
                                        list_add_tail(item, &amp;amp;l-&amp;gt;list)
                                          item-&amp;gt;next = &amp;amp;l-&amp;gt;list
                                          item-&amp;gt;prev = tail
    entry-&amp;gt;prev = entry&lt;/p&gt;
&lt;p&gt;The folio now sits on the list_lru with -&amp;gt;prev pointing to itself. The
next removal leaves the neighbours pointing t…&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/huge_memory: fix list corruption when deferred_split_scan() races with deferred_split_folio()&lt;/p&gt;
&lt;p&gt;Since the deferred split queue became a list_lru, the isolate callback
moves the folios it took a reference on to an on-stack list, linked
through folio-&amp;gt;_deferred_list, and deferred_split_scan() takes them off
that list with list_del_init() without holding the list_lru lock.&lt;/p&gt;
&lt;p&gt;deferred_split_folio() does not know about the on-stack list. It only
holds the list_lru lock when it looks at the same list_head, and it can
run for such a folio: a THP is queued when it is mapped, as a candidate
for the underused check, and is queued &amp;#34;again&amp;#34; when a part of it gets
unmapped:&lt;/p&gt;
&lt;p&gt;CPU0 deferred_split_scan()          CPU1 deferred_split_folio()
  list_del_init(&amp;amp;folio-&amp;gt;_deferred_list)
    next-&amp;gt;prev = prev
    prev-&amp;gt;next = next
    entry-&amp;gt;next = entry
                                      list_lru_lock_irqsave()
                                      folio_set_partially_mapped()
                                      __list_lru_add()
                                        list_empty(item)  -&amp;gt; true
                                        list_add_tail(item, &amp;amp;l-&amp;gt;list)
                                          item-&amp;gt;next = &amp;amp;l-&amp;gt;list
                                          item-&amp;gt;prev = tail
    entry-&amp;gt;prev = entry&lt;/p&gt;
&lt;p&gt;The folio now sits on the list_lru with -&amp;gt;prev pointing to itself. The
next removal leaves the neighbours pointing t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99728</guid>
    </item>
    <item>
      <title>GHSA-rcvj-j33h-jp62</title>
      <link>https://db.gcve.eu/vuln/ghsa-rcvj-j33h-jp62</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/huge_memory: fix list corruption when deferred_split_scan() races with deferred_split_folio()&lt;/p&gt;
&lt;p&gt;Since the deferred split queue became a list_lru, the isolate callback
moves the folios it took a reference on to an on-stack list, linked
through folio-&amp;gt;_deferred_list, and deferred_split_scan() takes them off
that list with list_del_init() without holding the list_lru lock.&lt;/p&gt;
&lt;p&gt;deferred_split_folio() does not know about the on-stack list. It only
holds the list_lru lock when it looks at the same list_head, and it can
run for such a folio: a THP is queued when it is mapped, as a candidate
for the underused check, and is queued &amp;#34;again&amp;#34; when a part of it gets
unmapped:&lt;/p&gt;
&lt;p&gt;CPU0 deferred_split_scan()          CPU1 deferred_split_folio()
  list_del_init(&amp;amp;folio-&amp;gt;_deferred_list)
    next-&amp;gt;prev = prev
    prev-&amp;gt;next = next
    entry-&amp;gt;next = entry
                                      list_lru_lock_irqsave()
                                      folio_set_partially_mapped()
                                      __list_lru_add()
                                        list_empty(item)  -&amp;gt; true
                                        list_add_tail(item, &amp;amp;l-&amp;gt;list)
                                          item-&amp;gt;next = &amp;amp;l-&amp;gt;list
                                          item-&amp;gt;prev = tail
    entry-&amp;gt;prev = entry&lt;/p&gt;
&lt;p&gt;The folio now sits on the list_lru with -&amp;gt;prev pointing to itself. The
next removal leaves the neighbours pointing t…&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/huge_memory: fix list corruption when deferred_split_scan() races with deferred_split_folio()&lt;/p&gt;
&lt;p&gt;Since the deferred split queue became a list_lru, the isolate callback
moves the folios it took a reference on to an on-stack list, linked
through folio-&amp;gt;_deferred_list, and deferred_split_scan() takes them off
that list with list_del_init() without holding the list_lru lock.&lt;/p&gt;
&lt;p&gt;deferred_split_folio() does not know about the on-stack list. It only
holds the list_lru lock when it looks at the same list_head, and it can
run for such a folio: a THP is queued when it is mapped, as a candidate
for the underused check, and is queued &amp;#34;again&amp;#34; when a part of it gets
unmapped:&lt;/p&gt;
&lt;p&gt;CPU0 deferred_split_scan()          CPU1 deferred_split_folio()
  list_del_init(&amp;amp;folio-&amp;gt;_deferred_list)
    next-&amp;gt;prev = prev
    prev-&amp;gt;next = next
    entry-&amp;gt;next = entry
                                      list_lru_lock_irqsave()
                                      folio_set_partially_mapped()
                                      __list_lru_add()
                                        list_empty(item)  -&amp;gt; true
                                        list_add_tail(item, &amp;amp;l-&amp;gt;list)
                                          item-&amp;gt;next = &amp;amp;l-&amp;gt;list
                                          item-&amp;gt;prev = tail
    entry-&amp;gt;prev = entry&lt;/p&gt;
&lt;p&gt;The folio now sits on the list_lru with -&amp;gt;prev pointing to itself. The
next removal leaves the neighbours pointing t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-rcvj-j33h-jp62</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>
