<?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>Wed, 07 Oct 2026 16:35:25 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-47119 — ext4: fix memory leak in ext4_fill_super</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-47119</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;ext4: fix memory leak in ext4_fill_super&lt;/p&gt;
&lt;p&gt;Buffer head references must be released before calling kill_bdev();
otherwise the buffer head (and its page referenced by b_data) will not
be freed by kill_bdev, and subsequently that bh will be leaked.&lt;/p&gt;
&lt;p&gt;If blocksizes differ, sb_set_blocksize() will kill current buffers and
page cache by using kill_bdev(). And then super block will be reread
again but using correct blocksize this time. sb_set_blocksize() didn&amp;#39;t
fully free superblock page and buffer head, and being busy, they were
not freed and instead leaked.&lt;/p&gt;
&lt;p&gt;This can easily be reproduced by calling an infinite loop of:&lt;/p&gt;
&lt;p&gt;systemctl start &amp;lt;ext4_on_lvm&amp;gt;.mount, and
  systemctl stop &amp;lt;ext4_on_lvm&amp;gt;.mount&lt;/p&gt;
&lt;p&gt;... since systemd creates a cgroup for each slice which it mounts, and
the bh leak get amplified by a dying memory cgroup that also never
gets freed, and memory consumption is much more easily noticed.&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;ext4: fix memory leak in ext4_fill_super&lt;/p&gt;
&lt;p&gt;Buffer head references must be released before calling kill_bdev();
otherwise the buffer head (and its page referenced by b_data) will not
be freed by kill_bdev, and subsequently that bh will be leaked.&lt;/p&gt;
&lt;p&gt;If blocksizes differ, sb_set_blocksize() will kill current buffers and
page cache by using kill_bdev(). And then super block will be reread
again but using correct blocksize this time. sb_set_blocksize() didn&amp;#39;t
fully free superblock page and buffer head, and being busy, they were
not freed and instead leaked.&lt;/p&gt;
&lt;p&gt;This can easily be reproduced by calling an infinite loop of:&lt;/p&gt;
&lt;p&gt;systemctl start &amp;lt;ext4_on_lvm&amp;gt;.mount, and
  systemctl stop &amp;lt;ext4_on_lvm&amp;gt;.mount&lt;/p&gt;
&lt;p&gt;... since systemd creates a cgroup for each slice which it mounts, and
the bh leak get amplified by a dying memory cgroup that also never
gets freed, and memory consumption is much more easily noticed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-47119</guid>
    </item>
  </channel>
</rss>
