<?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>Tue, 29 Sep 2026 09:32:48 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-97938 — reboot: fix cad_pid use-after-free race</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-97938</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;reboot: fix cad_pid use-after-free race&lt;/p&gt;
&lt;p&gt;cad_pid is a single kernel-wide struct pid pointer. proc_do_cad_pid()
reads it and passes it to pid_vnr() without protecting the lifetime of
the referenced struct pid. A concurrent writer can replace cad_pid and
drop the final reference to the old struct pid after the reader has
loaded the pointer but before pid_vnr() has finished dereferencing it,
causing a use-after-free.&lt;/p&gt;
&lt;p&gt;kill_cad_pid() has the same lifetime race when it passes cad_pid to
kill_pid().&lt;/p&gt;
&lt;p&gt;At the time this issue was reported, an unprivileged user could reach the
sysctl through user and PID namespaces because cad_pid was registered in
pid_table[]. Moving cad_pid back to the global reboot sysctl table
corrected that namespace and permission mismatch, but did not fix the
underlying lifetime race.&lt;/p&gt;
&lt;p&gt;Fix this by treating cad_pid as an RCU-protected pointer at both read
sites and by waiting for a grace period before dropping the old reference
on the write side.&lt;/p&gt;
&lt;p&gt;call_rcu(&amp;amp;old_pid-&amp;gt;rcu, ...) cannot be used here because free_pid()
also queues pid-&amp;gt;rcu; queueing the same rcu_head twice can corrupt the
RCU callback list.&lt;/p&gt;
&lt;p&gt;Original KASAN crash stack:
  kernel/pid.c:545 pid_nr_ns()        # reads freed pid-&amp;gt;level
  kernel/pid.c:556 pid_vnr()          # calls pid_nr_ns()
  kernel/pid.c:775 proc_do_cad_pid()  # calls pid_vnr(cad_pid)&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;reboot: fix cad_pid use-after-free race&lt;/p&gt;
&lt;p&gt;cad_pid is a single kernel-wide struct pid pointer. proc_do_cad_pid()
reads it and passes it to pid_vnr() without protecting the lifetime of
the referenced struct pid. A concurrent writer can replace cad_pid and
drop the final reference to the old struct pid after the reader has
loaded the pointer but before pid_vnr() has finished dereferencing it,
causing a use-after-free.&lt;/p&gt;
&lt;p&gt;kill_cad_pid() has the same lifetime race when it passes cad_pid to
kill_pid().&lt;/p&gt;
&lt;p&gt;At the time this issue was reported, an unprivileged user could reach the
sysctl through user and PID namespaces because cad_pid was registered in
pid_table[]. Moving cad_pid back to the global reboot sysctl table
corrected that namespace and permission mismatch, but did not fix the
underlying lifetime race.&lt;/p&gt;
&lt;p&gt;Fix this by treating cad_pid as an RCU-protected pointer at both read
sites and by waiting for a grace period before dropping the old reference
on the write side.&lt;/p&gt;
&lt;p&gt;call_rcu(&amp;amp;old_pid-&amp;gt;rcu, ...) cannot be used here because free_pid()
also queues pid-&amp;gt;rcu; queueing the same rcu_head twice can corrupt the
RCU callback list.&lt;/p&gt;
&lt;p&gt;Original KASAN crash stack:
  kernel/pid.c:545 pid_nr_ns()        # reads freed pid-&amp;gt;level
  kernel/pid.c:556 pid_vnr()          # calls pid_nr_ns()
  kernel/pid.c:775 proc_do_cad_pid()  # calls pid_vnr(cad_pid)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-97938</guid>
    </item>
  </channel>
</rss>
