<?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:20:28.965841+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/cve-2026-99698</id>
    <title>CVE-2026-99698 — mm/cma: accept memory of CMA areas reserved at a fixed address</title>
    <updated>2026-11-20T21:20:28.967653+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>mm/cma: accept memory of CMA areas reserved at a fixed address</p>
<p>CMA areas allocated from memblock have their memory accepted by
memblock_alloc_range_nid(), but areas reserved at a fixed address with
memblock_reserve() are not.</p>
<p>If a fixed CMA area is requested by the cma=&lt;size&gt;@&lt;base&gt; command line
parameter, it may be in regular RAM and on TDX and SEV-SNP guests it
must be accepted.</p>
<p>Accept the memory of fixed CMA areas as well, so that all CMA areas are
accepted regardless of how they were reserved.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-99698"/>
  </entry>
</feed>
