<?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:14.159981+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-99706</id>
    <title>fkie_cve-2026-99706</title>
    <updated>2026-11-20T21:04:14.163839+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: fix address wraparound when scanning large folio PTEs</p>
<p>numa_rebuild_large_mapping() and do_swap_page() can be tricked into
generating an address wraparound, crashing the kernel. All that's required
is to map a tail page of a large folio close enough to the start/end of
the address space to e.g., make</p>
<p>unsigned long addr_start = addr - (nr &lt;&lt; PAGE_SHIFT);</p>
<p>to wrap around.</p>
<p>Let's fix it by providing a better helper, folio_scan_range(), that
takes care of staying within VMA and page table boundaries while
handling possible wraparounds.</p>
<p>There are some nasty details, like not being able to use pmd_addr_end()
in this context. Add some helpful comments for these cases.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-99706"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-9qmh-9hx3-4c73</id>
    <title>GHSA-9qmh-9hx3-4c73</title>
    <updated>2026-11-20T21:04:14.163926+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: fix address wraparound when scanning large folio PTEs</p>
<p>numa_rebuild_large_mapping() and do_swap_page() can be tricked into
generating an address wraparound, crashing the kernel. All that's required
is to map a tail page of a large folio close enough to the start/end of
the address space to e.g., make</p>
<p>unsigned long addr_start = addr - (nr &lt;&lt; PAGE_SHIFT);</p>
<p>to wrap around.</p>
<p>Let's fix it by providing a better helper, folio_scan_range(), that
takes care of staying within VMA and page table boundaries while
handling possible wraparounds.</p>
<p>There are some nasty details, like not being able to use pmd_addr_end()
in this context. Add some helpful comments for these cases.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-9qmh-9hx3-4c73"/>
  </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:14.163956+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>
