<?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:58.528764+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-99699</id>
    <title>fkie_cve-2026-99699</title>
    <updated>2026-11-20T21:04:58.532408+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/cma: accept memory of multi-range CMA areas</p>
<p>Patch series "mm/cma: accept memory of CMA areas reserved with
memblock_reserve()", v1.</p>
<p>Pages of allocated CMA areas are released to the buddy allocator with
__free_pages(), which does not check for unaccepted memory.</p>
<p>This usually works because memblock accepts the memory it allocates.</p>
<p>However, multi-range CMA areas, used by hugetlb_cma, and fixed CMA areas
requested with cma=&lt;size&gt;@&lt;base&gt; are reserved with memblock_reserve() and
their memory is never accepted.</p>
<p>On TDX and SEV-SNP guests the first access to such a page is fatal.</p>
<p>To ease the backporting, each case is addressed by a separate patch:
- patch 1 accepts the memory of multi-range CMA areas
- patch 2 does the same for the fixed CMA areas</p>
<p>The second patch won't apply cleanly to 6.6 and 6.12, but I believe the
stable team LLMs will take care of that :)</p>
<p>This patch (of 2):</p>
<p>On systems with unaccepted memory, memblock allocations accept the
allocated range, but when cma_declare_contiguous_multi() uses open coded
allocation of multiple ranges, it reserves them with memblock_reserve()
and they are never accepted.</p>
<p>These pages are released to the buddy allocator by cma_activate_area()
with __free_pages() that does not check for unaccepted memory, so the
first access to such a page in a TDX or SEV-SNP guest is fatal.</p>
<p>Accept the memory of each range when it is reserved.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-99699"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-g9wh-4633-88gc</id>
    <title>GHSA-g9wh-4633-88gc</title>
    <updated>2026-11-20T21:04:58.532492+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/cma: accept memory of multi-range CMA areas</p>
<p>Patch series "mm/cma: accept memory of CMA areas reserved with
memblock_reserve()", v1.</p>
<p>Pages of allocated CMA areas are released to the buddy allocator with
__free_pages(), which does not check for unaccepted memory.</p>
<p>This usually works because memblock accepts the memory it allocates.</p>
<p>However, multi-range CMA areas, used by hugetlb_cma, and fixed CMA areas
requested with cma=&lt;size&gt;@&lt;base&gt; are reserved with memblock_reserve() and
their memory is never accepted.</p>
<p>On TDX and SEV-SNP guests the first access to such a page is fatal.</p>
<p>To ease the backporting, each case is addressed by a separate patch:
- patch 1 accepts the memory of multi-range CMA areas
- patch 2 does the same for the fixed CMA areas</p>
<p>The second patch won't apply cleanly to 6.6 and 6.12, but I believe the
stable team LLMs will take care of that :)</p>
<p>This patch (of 2):</p>
<p>On systems with unaccepted memory, memblock allocations accept the
allocated range, but when cma_declare_contiguous_multi() uses open coded
allocation of multiple ranges, it reserves them with memblock_reserve()
and they are never accepted.</p>
<p>These pages are released to the buddy allocator by cma_activate_area()
with __free_pages() that does not check for unaccepted memory, so the
first access to such a page in a TDX or SEV-SNP guest is fatal.</p>
<p>Accept the memory of each range when it is reserved.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-g9wh-4633-88gc"/>
  </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:58.532528+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>
