<?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>Sat, 03 Oct 2026 07:25:32 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90325 — blk-cgroup: skip dying blkg in blkcg_activate_policy()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90325</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: skip dying blkg in blkcg_activate_policy()&lt;/p&gt;
&lt;p&gt;When switching IO schedulers on a block device, blkcg_activate_policy()
can race with concurrent blkcg deletion, leading to a use-after-free in
rcu_accelerate_cbs.&lt;/p&gt;
&lt;p&gt;T1:                               T2:
                                  blkg_destroy
                                  kill(&amp;amp;blkg-&amp;gt;refcnt) // blkg-&amp;gt;refcnt=1-&amp;gt;0
                                  blkg_release // call_rcu(__blkg_release)
                                  ...
                                  blkg_free_workfn
                                  -&amp;gt;pd_free_fn(pd)
elv_iosched_store
elevator_switch
...
iterate blkg list
blkg_get(blkg) // blkg-&amp;gt;refcnt=0-&amp;gt;1
                                  list_del_init(&amp;amp;blkg-&amp;gt;q_node)
blkg_put(pinned_blkg) // blkg-&amp;gt;refcnt=1-&amp;gt;0
blkg_release // call_rcu again
rcu_accelerate_cbs // uaf&lt;/p&gt;
&lt;p&gt;Fix this by checking hlist_unhashed(&amp;amp;blkg-&amp;gt;blkcg_node) before getting
a reference to the blkg. This is the same check used in blkg_destroy()
to detect if a blkg has already been destroyed. If the blkg is already
unhashed, skip processing it since it&amp;#39;s being destroyed.&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: skip dying blkg in blkcg_activate_policy()&lt;/p&gt;
&lt;p&gt;When switching IO schedulers on a block device, blkcg_activate_policy()
can race with concurrent blkcg deletion, leading to a use-after-free in
rcu_accelerate_cbs.&lt;/p&gt;
&lt;p&gt;T1:                               T2:
                                  blkg_destroy
                                  kill(&amp;amp;blkg-&amp;gt;refcnt) // blkg-&amp;gt;refcnt=1-&amp;gt;0
                                  blkg_release // call_rcu(__blkg_release)
                                  ...
                                  blkg_free_workfn
                                  -&amp;gt;pd_free_fn(pd)
elv_iosched_store
elevator_switch
...
iterate blkg list
blkg_get(blkg) // blkg-&amp;gt;refcnt=0-&amp;gt;1
                                  list_del_init(&amp;amp;blkg-&amp;gt;q_node)
blkg_put(pinned_blkg) // blkg-&amp;gt;refcnt=1-&amp;gt;0
blkg_release // call_rcu again
rcu_accelerate_cbs // uaf&lt;/p&gt;
&lt;p&gt;Fix this by checking hlist_unhashed(&amp;amp;blkg-&amp;gt;blkcg_node) before getting
a reference to the blkg. This is the same check used in blkg_destroy()
to detect if a blkg has already been destroyed. If the blkg is already
unhashed, skip processing it since it&amp;#39;s being destroyed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90325</guid>
    </item>
  </channel>
</rss>
