<?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://cve.radiocsirt.org</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>Sun, 04 Oct 2026 04:30:10 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-14605</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-14605</link>
      <description>bdu:2025-14605</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-14605</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0496 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0496</link>
      <description>certfr-2024-avi-0496</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0496</guid>
    </item>
    <item>
      <title>EUVD-2026-309696</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309696</link>
      <description>EUVD-2026-309696</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309696</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47365</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47365</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;afs: Fix page leak&lt;/p&gt;
&lt;p&gt;There&amp;#39;s a loop in afs_extend_writeback() that adds extra pages to a write
we want to make to improve the efficiency of the writeback by making it
larger.  This loop stops, however, if we hit a page we can&amp;#39;t write back
from immediately, but it doesn&amp;#39;t get rid of the page ref we speculatively
acquired.&lt;/p&gt;
&lt;p&gt;This was caused by the removal of the cleanup loop when the code switched
from using find_get_pages_contig() to xarray scanning as the latter only
gets a single page at a time, not a batch.&lt;/p&gt;
&lt;p&gt;Fix this by putting the page on a ref on an early break from the loop.
Unfortunately, we can&amp;#39;t just add that page to the pagevec we&amp;#39;re employing
as we&amp;#39;ll go through that and add those pages to the RPC call.&lt;/p&gt;
&lt;p&gt;This was found by the generic/074 test.  It leaks ~4GiB of RAM each time it
is run - which can be observed with &amp;#34;top&amp;#34;.&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;afs: Fix page leak&lt;/p&gt;
&lt;p&gt;There&amp;#39;s a loop in afs_extend_writeback() that adds extra pages to a write
we want to make to improve the efficiency of the writeback by making it
larger.  This loop stops, however, if we hit a page we can&amp;#39;t write back
from immediately, but it doesn&amp;#39;t get rid of the page ref we speculatively
acquired.&lt;/p&gt;
&lt;p&gt;This was caused by the removal of the cleanup loop when the code switched
from using find_get_pages_contig() to xarray scanning as the latter only
gets a single page at a time, not a batch.&lt;/p&gt;
&lt;p&gt;Fix this by putting the page on a ref on an early break from the loop.
Unfortunately, we can&amp;#39;t just add that page to the pagevec we&amp;#39;re employing
as we&amp;#39;ll go through that and add those pages to the RPC call.&lt;/p&gt;
&lt;p&gt;This was found by the generic/074 test.  It leaks ~4GiB of RAM each time it
is run - which can be observed with &amp;#34;top&amp;#34;.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47365</guid>
    </item>
    <item>
      <title>GHSA-95jq-x6q9-c9cq</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-95jq-x6q9-c9cq</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;afs: Fix page leak&lt;/p&gt;
&lt;p&gt;There&amp;#39;s a loop in afs_extend_writeback() that adds extra pages to a write
we want to make to improve the efficiency of the writeback by making it
larger.  This loop stops, however, if we hit a page we can&amp;#39;t write back
from immediately, but it doesn&amp;#39;t get rid of the page ref we speculatively
acquired.&lt;/p&gt;
&lt;p&gt;This was caused by the removal of the cleanup loop when the code switched
from using find_get_pages_contig() to xarray scanning as the latter only
gets a single page at a time, not a batch.&lt;/p&gt;
&lt;p&gt;Fix this by putting the page on a ref on an early break from the loop.
Unfortunately, we can&amp;#39;t just add that page to the pagevec we&amp;#39;re employing
as we&amp;#39;ll go through that and add those pages to the RPC call.&lt;/p&gt;
&lt;p&gt;This was found by the generic/074 test.  It leaks ~4GiB of RAM each time it
is run - which can be observed with &amp;#34;top&amp;#34;.&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;afs: Fix page leak&lt;/p&gt;
&lt;p&gt;There&amp;#39;s a loop in afs_extend_writeback() that adds extra pages to a write
we want to make to improve the efficiency of the writeback by making it
larger.  This loop stops, however, if we hit a page we can&amp;#39;t write back
from immediately, but it doesn&amp;#39;t get rid of the page ref we speculatively
acquired.&lt;/p&gt;
&lt;p&gt;This was caused by the removal of the cleanup loop when the code switched
from using find_get_pages_contig() to xarray scanning as the latter only
gets a single page at a time, not a batch.&lt;/p&gt;
&lt;p&gt;Fix this by putting the page on a ref on an early break from the loop.
Unfortunately, we can&amp;#39;t just add that page to the pagevec we&amp;#39;re employing
as we&amp;#39;ll go through that and add those pages to the RPC call.&lt;/p&gt;
&lt;p&gt;This was found by the generic/074 test.  It leaks ~4GiB of RAM each time it
is run - which can be observed with &amp;#34;top&amp;#34;.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-95jq-x6q9-c9cq</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2008-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:2008-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2024:2008-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47365</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47365</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: afs: Fix page leak There&amp;#39;s a loop in afs_extend_writeback() that adds extra pages to a write we want to make to improve the efficiency of the writeback by making it larger.  This loop stops, however, if we hit a page we can&amp;#39;t write back from immediately, but it doesn&amp;#39;t get rid of the page ref we speculatively acquired. This was caused by the removal of the cleanup loop when the code switched from using find_get_pages_contig() to xarray scanning as the latter only gets a single page at a time, not a batch. Fix this by putting the page on a ref on an early break from the loop. Unfortunately, we can&amp;#39;t just add that page to the pagevec we&amp;#39;re employing as we&amp;#39;ll go through that and add those pages to the RPC call. This was found by the generic/074 test.  It leaks ~4GiB of RAM each time it is run - which can be observed with &amp;#34;top&amp;#34;.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: afs: Fix page leak There&amp;#39;s a loop in afs_extend_writeback() that adds extra pages to a write we want to make to improve the efficiency of the writeback by making it larger.  This loop stops, however, if we hit a page we can&amp;#39;t write back from immediately, but it doesn&amp;#39;t get rid of the page ref we speculatively acquired. This was caused by the removal of the cleanup loop when the code switched from using find_get_pages_contig() to xarray scanning as the latter only gets a single page at a time, not a batch. Fix this by putting the page on a ref on an early break from the loop. Unfortunately, we can&amp;#39;t just add that page to the pagevec we&amp;#39;re employing as we&amp;#39;ll go through that and add those pages to the RPC call. This was found by the generic/074 test.  It leaks ~4GiB of RAM each time it is run - which can be observed with &amp;#34;top&amp;#34;.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47365</guid>
    </item>
  </channel>
</rss>
