<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-20T21:04:03.490197+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-99728</id>
    <title>fkie_cve-2026-99728</title>
    <updated>2026-11-20T21:04:03.494105+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>mm/huge_memory: fix list corruption when deferred_split_scan() races with deferred_split_folio()</p>
<p>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-&gt;_deferred_list, and deferred_split_scan() takes them off
that list with list_del_init() without holding the list_lru lock.</p>
<p>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 "again" when a part of it gets
unmapped:</p>
<p>CPU0 deferred_split_scan()          CPU1 deferred_split_folio()
  list_del_init(&amp;folio-&gt;_deferred_list)
    next-&gt;prev = prev
    prev-&gt;next = next
    entry-&gt;next = entry
                                      list_lru_lock_irqsave()
                                      folio_set_partially_mapped()
                                      __list_lru_add()
                                        list_empty(item)  -&gt; true
                                        list_add_tail(item, &amp;l-&gt;list)
                                          item-&gt;next = &amp;l-&gt;list
                                          item-&gt;prev = tail
    entry-&gt;prev = entry</p>
<p>The folio now sits on the list_lru with -&gt;prev pointing to itself. The
next removal leaves the neighbours pointing t…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-99728"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-rcvj-j33h-jp62</id>
    <title>GHSA-rcvj-j33h-jp62</title>
    <updated>2026-11-20T21:04:03.494234+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>mm/huge_memory: fix list corruption when deferred_split_scan() races with deferred_split_folio()</p>
<p>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-&gt;_deferred_list, and deferred_split_scan() takes them off
that list with list_del_init() without holding the list_lru lock.</p>
<p>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 "again" when a part of it gets
unmapped:</p>
<p>CPU0 deferred_split_scan()          CPU1 deferred_split_folio()
  list_del_init(&amp;folio-&gt;_deferred_list)
    next-&gt;prev = prev
    prev-&gt;next = next
    entry-&gt;next = entry
                                      list_lru_lock_irqsave()
                                      folio_set_partially_mapped()
                                      __list_lru_add()
                                        list_empty(item)  -&gt; true
                                        list_add_tail(item, &amp;l-&gt;list)
                                          item-&gt;next = &amp;l-&gt;list
                                          item-&gt;prev = tail
    entry-&gt;prev = entry</p>
<p>The folio now sits on the list_lru with -&gt;prev pointing to itself. The
next removal leaves the neighbours pointing t…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-rcvj-j33h-jp62"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</id>
    <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
    <updated>2026-11-20T21:04:03.494283+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/wid-sec-w-2026-4695"/>
  </entry>
</feed>
