<?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:27:39 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99699</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99699</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/cma: accept memory of multi-range CMA areas&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;mm/cma: accept memory of CMA areas reserved with
memblock_reserve()&amp;#34;, v1.&lt;/p&gt;
&lt;p&gt;Pages of allocated CMA areas are released to the buddy allocator with
__free_pages(), which does not check for unaccepted memory.&lt;/p&gt;
&lt;p&gt;This usually works because memblock accepts the memory it allocates.&lt;/p&gt;
&lt;p&gt;However, multi-range CMA areas, used by hugetlb_cma, and fixed CMA areas
requested with cma=&amp;lt;size&amp;gt;@&amp;lt;base&amp;gt; are reserved with memblock_reserve() and
their memory is never accepted.&lt;/p&gt;
&lt;p&gt;On TDX and SEV-SNP guests the first access to such a page is fatal.&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;The second patch won&amp;#39;t apply cleanly to 6.6 and 6.12, but I believe the
stable team LLMs will take care of that :)&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Accept the memory of each range when it is reserved.&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/cma: accept memory of multi-range CMA areas&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;mm/cma: accept memory of CMA areas reserved with
memblock_reserve()&amp;#34;, v1.&lt;/p&gt;
&lt;p&gt;Pages of allocated CMA areas are released to the buddy allocator with
__free_pages(), which does not check for unaccepted memory.&lt;/p&gt;
&lt;p&gt;This usually works because memblock accepts the memory it allocates.&lt;/p&gt;
&lt;p&gt;However, multi-range CMA areas, used by hugetlb_cma, and fixed CMA areas
requested with cma=&amp;lt;size&amp;gt;@&amp;lt;base&amp;gt; are reserved with memblock_reserve() and
their memory is never accepted.&lt;/p&gt;
&lt;p&gt;On TDX and SEV-SNP guests the first access to such a page is fatal.&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;The second patch won&amp;#39;t apply cleanly to 6.6 and 6.12, but I believe the
stable team LLMs will take care of that :)&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Accept the memory of each range when it is reserved.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99699</guid>
    </item>
    <item>
      <title>GHSA-g9wh-4633-88gc</title>
      <link>https://db.gcve.eu/vuln/ghsa-g9wh-4633-88gc</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/cma: accept memory of multi-range CMA areas&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;mm/cma: accept memory of CMA areas reserved with
memblock_reserve()&amp;#34;, v1.&lt;/p&gt;
&lt;p&gt;Pages of allocated CMA areas are released to the buddy allocator with
__free_pages(), which does not check for unaccepted memory.&lt;/p&gt;
&lt;p&gt;This usually works because memblock accepts the memory it allocates.&lt;/p&gt;
&lt;p&gt;However, multi-range CMA areas, used by hugetlb_cma, and fixed CMA areas
requested with cma=&amp;lt;size&amp;gt;@&amp;lt;base&amp;gt; are reserved with memblock_reserve() and
their memory is never accepted.&lt;/p&gt;
&lt;p&gt;On TDX and SEV-SNP guests the first access to such a page is fatal.&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;The second patch won&amp;#39;t apply cleanly to 6.6 and 6.12, but I believe the
stable team LLMs will take care of that :)&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Accept the memory of each range when it is reserved.&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/cma: accept memory of multi-range CMA areas&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;mm/cma: accept memory of CMA areas reserved with
memblock_reserve()&amp;#34;, v1.&lt;/p&gt;
&lt;p&gt;Pages of allocated CMA areas are released to the buddy allocator with
__free_pages(), which does not check for unaccepted memory.&lt;/p&gt;
&lt;p&gt;This usually works because memblock accepts the memory it allocates.&lt;/p&gt;
&lt;p&gt;However, multi-range CMA areas, used by hugetlb_cma, and fixed CMA areas
requested with cma=&amp;lt;size&amp;gt;@&amp;lt;base&amp;gt; are reserved with memblock_reserve() and
their memory is never accepted.&lt;/p&gt;
&lt;p&gt;On TDX and SEV-SNP guests the first access to such a page is fatal.&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;The second patch won&amp;#39;t apply cleanly to 6.6 and 6.12, but I believe the
stable team LLMs will take care of that :)&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Accept the memory of each range when it is reserved.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-g9wh-4633-88gc</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>
