<?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-09-29T02:21:14.382600+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-93795</id>
    <title>CVE-2026-93795 — blk-cgroup: fix leaks and online flag on radix_tree_insert failure</title>
    <updated>2026-09-29T02:21:14.714135+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: fix leaks and online flag on radix_tree_insert failure</p>
<p>When radix_tree_insert() fails in blkg_create(), the error path has two
issues:</p>
<p>1. blkg-&gt;online is set to true unconditionally, even when the blkg was
   never fully inserted.  Move the assignment inside the success block.</p>
<p>2. The error path calls blkg_put() without first calling
   percpu_ref_kill().  Because the refcount is still in percpu mode,
   percpu_ref_put() only does this_cpu_sub() without checking for zero,
   so blkg_release() is never triggered.  This permanently leaks the
   blkg memory, its percpu iostat, policy data, the parent blkg
   reference, and the cgroup css reference — the latter preventing the
   cgroup from ever being destroyed.</p>
<p>Fix by replacing blkg_put() with percpu_ref_kill(), matching the pattern
used in blkg_destroy().</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-93795"/>
  </entry>
</feed>
