<?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:04:58 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99645</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99645</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/cma: don&amp;#39;t release CMA pages still in use&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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-&amp;gt;lru, corrupting buddy lists.&lt;/p&gt;
&lt;p&gt;Avoid the corruption by not freeing a CMA region if any of the
pages inside are still in use.&lt;/p&gt;
&lt;p&gt;Make it explicit in the warning that the driver allowed a leak.&lt;/p&gt;
&lt;p&gt;While at it, use page_ref_freeze() to make the semantics clearer and
switch to pr_warn_ratelimited().&lt;/p&gt;
&lt;p&gt;[ david: use page_ref_freeze() + pr_warn_ratelimited() ]&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: don&amp;#39;t release CMA pages still in use&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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-&amp;gt;lru, corrupting buddy lists.&lt;/p&gt;
&lt;p&gt;Avoid the corruption by not freeing a CMA region if any of the
pages inside are still in use.&lt;/p&gt;
&lt;p&gt;Make it explicit in the warning that the driver allowed a leak.&lt;/p&gt;
&lt;p&gt;While at it, use page_ref_freeze() to make the semantics clearer and
switch to pr_warn_ratelimited().&lt;/p&gt;
&lt;p&gt;[ david: use page_ref_freeze() + pr_warn_ratelimited() ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99645</guid>
    </item>
    <item>
      <title>GHSA-646v-9cch-4hmg</title>
      <link>https://db.gcve.eu/vuln/ghsa-646v-9cch-4hmg</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/cma: don&amp;#39;t release CMA pages still in use&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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-&amp;gt;lru, corrupting buddy lists.&lt;/p&gt;
&lt;p&gt;Avoid the corruption by not freeing a CMA region if any of the
pages inside are still in use.&lt;/p&gt;
&lt;p&gt;Make it explicit in the warning that the driver allowed a leak.&lt;/p&gt;
&lt;p&gt;While at it, use page_ref_freeze() to make the semantics clearer and
switch to pr_warn_ratelimited().&lt;/p&gt;
&lt;p&gt;[ david: use page_ref_freeze() + pr_warn_ratelimited() ]&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: don&amp;#39;t release CMA pages still in use&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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-&amp;gt;lru, corrupting buddy lists.&lt;/p&gt;
&lt;p&gt;Avoid the corruption by not freeing a CMA region if any of the
pages inside are still in use.&lt;/p&gt;
&lt;p&gt;Make it explicit in the warning that the driver allowed a leak.&lt;/p&gt;
&lt;p&gt;While at it, use page_ref_freeze() to make the semantics clearer and
switch to pr_warn_ratelimited().&lt;/p&gt;
&lt;p&gt;[ david: use page_ref_freeze() + pr_warn_ratelimited() ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-646v-9cch-4hmg</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>
