<?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:56.791954+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-99645</id>
    <title>fkie_cve-2026-99645</title>
    <updated>2026-11-20T21:04:56.795424+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: don't release CMA pages still in use</p>
<p>When a driver calls dma_free_contiguous() before quiescing DMA, the
page might still have a reference from the device.
put_page_testzero() there returns false, WARN fires, but the code proceeds
to free_contig_frozen_range() putting a live page onto buddy and clearing
the bitmap. A subsequent allocation can hand the same PFN to a new
owner while the original holder still references it.</p>
<p>A concurrent put_page() that drops the last reference between the
testzero loop and free_contig_frozen_range() can double-queue the page
via page-&gt;lru, corrupting buddy lists.</p>
<p>Avoid the corruption by not freeing a CMA region if any of the
pages inside are still in use.</p>
<p>Make it explicit in the warning that the driver allowed a leak.</p>
<p>While at it, use page_ref_freeze() to make the semantics clearer and
switch to pr_warn_ratelimited().</p>
<p>[ david: use page_ref_freeze() + pr_warn_ratelimited() ]</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-99645"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-646v-9cch-4hmg</id>
    <title>GHSA-646v-9cch-4hmg</title>
    <updated>2026-11-20T21:04:56.795561+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: don't release CMA pages still in use</p>
<p>When a driver calls dma_free_contiguous() before quiescing DMA, the
page might still have a reference from the device.
put_page_testzero() there returns false, WARN fires, but the code proceeds
to free_contig_frozen_range() putting a live page onto buddy and clearing
the bitmap. A subsequent allocation can hand the same PFN to a new
owner while the original holder still references it.</p>
<p>A concurrent put_page() that drops the last reference between the
testzero loop and free_contig_frozen_range() can double-queue the page
via page-&gt;lru, corrupting buddy lists.</p>
<p>Avoid the corruption by not freeing a CMA region if any of the
pages inside are still in use.</p>
<p>Make it explicit in the warning that the driver allowed a leak.</p>
<p>While at it, use page_ref_freeze() to make the semantics clearer and
switch to pr_warn_ratelimited().</p>
<p>[ david: use page_ref_freeze() + pr_warn_ratelimited() ]</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-646v-9cch-4hmg"/>
  </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:56.795610+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>
