<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T19:41:41.530607+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-90325</id>
    <title>CVE-2026-90325 — blk-cgroup: skip dying blkg in blkcg_activate_policy()</title>
    <updated>2026-10-03T19:41:41.532902+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>blk-cgroup: skip dying blkg in blkcg_activate_policy()</p>
<p>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.</p>
<p>T1:                               T2:
                                  blkg_destroy
                                  kill(&amp;blkg-&gt;refcnt) // blkg-&gt;refcnt=1-&gt;0
                                  blkg_release // call_rcu(__blkg_release)
                                  ...
                                  blkg_free_workfn
                                  -&gt;pd_free_fn(pd)
elv_iosched_store
elevator_switch
...
iterate blkg list
blkg_get(blkg) // blkg-&gt;refcnt=0-&gt;1
                                  list_del_init(&amp;blkg-&gt;q_node)
blkg_put(pinned_blkg) // blkg-&gt;refcnt=1-&gt;0
blkg_release // call_rcu again
rcu_accelerate_cbs // uaf</p>
<p>Fix this by checking hlist_unhashed(&amp;blkg-&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's being destroyed.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-90325"/>
  </entry>
</feed>
