<?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>Fri, 02 Oct 2026 05:36:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53421 — blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53421</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;blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats()&lt;/p&gt;
&lt;p&gt;When blkg_alloc() is called to allocate a blkcg_gq structure
with the associated blkg_iostat_set&amp;#39;s, there are 2 fields within
blkg_iostat_set that requires proper initialization - blkg &amp;amp; sync.
The former field was introduced by commit 3b8cc6298724 (&amp;#34;blk-cgroup:
Optimize blkcg_rstat_flush()&amp;#34;) while the later one was introduced by
commit f73316482977 (&amp;#34;blk-cgroup: reimplement basic IO stats using
cgroup rstat&amp;#34;).&lt;/p&gt;
&lt;p&gt;Unfortunately those fields in the blkg_iostat_set&amp;#39;s are not properly
re-initialized when they are cleared in v1&amp;#39;s blkcg_reset_stats(). This
can lead to a kernel panic due to NULL pointer access of the blkg
pointer. The missing initialization of sync is less problematic and
can be a problem in a debug kernel due to missing lockdep initialization.&lt;/p&gt;
&lt;p&gt;Fix these problems by re-initializing them after memory clearing.&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;blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats()&lt;/p&gt;
&lt;p&gt;When blkg_alloc() is called to allocate a blkcg_gq structure
with the associated blkg_iostat_set&amp;#39;s, there are 2 fields within
blkg_iostat_set that requires proper initialization - blkg &amp;amp; sync.
The former field was introduced by commit 3b8cc6298724 (&amp;#34;blk-cgroup:
Optimize blkcg_rstat_flush()&amp;#34;) while the later one was introduced by
commit f73316482977 (&amp;#34;blk-cgroup: reimplement basic IO stats using
cgroup rstat&amp;#34;).&lt;/p&gt;
&lt;p&gt;Unfortunately those fields in the blkg_iostat_set&amp;#39;s are not properly
re-initialized when they are cleared in v1&amp;#39;s blkcg_reset_stats(). This
can lead to a kernel panic due to NULL pointer access of the blkg
pointer. The missing initialization of sync is less problematic and
can be a problem in a debug kernel due to missing lockdep initialization.&lt;/p&gt;
&lt;p&gt;Fix these problems by re-initializing them after memory clearing.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53421</guid>
    </item>
  </channel>
</rss>
