<?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://vulnerability.circl.lu</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>Thu, 01 Oct 2026 14:03:00 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-47365 — afs: Fix page leak</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2021-47365</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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://vulnerability.circl.lu/vuln/cve-2021-47365</guid>
    </item>
  </channel>
</rss>
