<?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>Mon, 28 Sep 2026 23:12:58 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-97903</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-97903</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;exit: hold a reference to thread_pid across proc_flush_pid&lt;/p&gt;
&lt;p&gt;Commit 0a36bad01731 (&amp;#34;release_task: kill the no longer needed
get/put_pid(thread_pid)&amp;#34;) removed the reference around proc_flush_pid().
It assumed that free_pids(post.pids) at the end of release_task() would
keep thread_pid alive until then.&lt;/p&gt;
&lt;p&gt;That assumption is wrong.  __change_pid() only records a detached PID in
post.pids when pid_has_task() is false for every PIDTYPE.  If another task
still uses the exiting task&amp;#39;s PID as its process group or session ID,
__unhash_process() removes the exiting task&amp;#39;s PIDTYPE_PID link but leaves
the PID out of post.pids.  release_task() therefore holds no reference to
it after dropping tasklist_lock.&lt;/p&gt;
&lt;p&gt;The other task can then remove the remaining PIDTYPE links.  Its
free_pids() call schedules delayed_put_pid(), and the RCU callback can free
the PID before the first release_task() reaches proc_flush_pid().&lt;/p&gt;
&lt;p&gt;An unprivileged reproducer races wait4(-1) against setsid() to trigger this
ordering.  Three of three fresh v7.2 KASAN boots reported:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in
    proc_invalidate_siblings_dcache+0x3e2/0x3f0
    Read of size 8 by task h7_pid_reaper/1921&lt;/p&gt;
&lt;p&gt;Call Trace:
     proc_invalidate_siblings_dcache
     release_task
     wait_consider_task
     __do_wait
     do_wait
     kernel_wait4&lt;/p&gt;
&lt;p&gt;Freed by task 0:
     kmem_cache_free
     put_pid
     delayed_put_pid
     rcu_core&lt;/p&gt;
&lt;p&gt;Last potentia…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;exit: hold a reference to thread_pid across proc_flush_pid&lt;/p&gt;
&lt;p&gt;Commit 0a36bad01731 (&amp;#34;release_task: kill the no longer needed
get/put_pid(thread_pid)&amp;#34;) removed the reference around proc_flush_pid().
It assumed that free_pids(post.pids) at the end of release_task() would
keep thread_pid alive until then.&lt;/p&gt;
&lt;p&gt;That assumption is wrong.  __change_pid() only records a detached PID in
post.pids when pid_has_task() is false for every PIDTYPE.  If another task
still uses the exiting task&amp;#39;s PID as its process group or session ID,
__unhash_process() removes the exiting task&amp;#39;s PIDTYPE_PID link but leaves
the PID out of post.pids.  release_task() therefore holds no reference to
it after dropping tasklist_lock.&lt;/p&gt;
&lt;p&gt;The other task can then remove the remaining PIDTYPE links.  Its
free_pids() call schedules delayed_put_pid(), and the RCU callback can free
the PID before the first release_task() reaches proc_flush_pid().&lt;/p&gt;
&lt;p&gt;An unprivileged reproducer races wait4(-1) against setsid() to trigger this
ordering.  Three of three fresh v7.2 KASAN boots reported:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in
    proc_invalidate_siblings_dcache+0x3e2/0x3f0
    Read of size 8 by task h7_pid_reaper/1921&lt;/p&gt;
&lt;p&gt;Call Trace:
     proc_invalidate_siblings_dcache
     release_task
     wait_consider_task
     __do_wait
     do_wait
     kernel_wait4&lt;/p&gt;
&lt;p&gt;Freed by task 0:
     kmem_cache_free
     put_pid
     delayed_put_pid
     rcu_core&lt;/p&gt;
&lt;p&gt;Last potentia…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-97903</guid>
    </item>
    <item>
      <title>GHSA-cpwj-27c2-jfgq</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-cpwj-27c2-jfgq</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;exit: hold a reference to thread_pid across proc_flush_pid&lt;/p&gt;
&lt;p&gt;Commit 0a36bad01731 (&amp;#34;release_task: kill the no longer needed
get/put_pid(thread_pid)&amp;#34;) removed the reference around proc_flush_pid().
It assumed that free_pids(post.pids) at the end of release_task() would
keep thread_pid alive until then.&lt;/p&gt;
&lt;p&gt;That assumption is wrong.  __change_pid() only records a detached PID in
post.pids when pid_has_task() is false for every PIDTYPE.  If another task
still uses the exiting task&amp;#39;s PID as its process group or session ID,
__unhash_process() removes the exiting task&amp;#39;s PIDTYPE_PID link but leaves
the PID out of post.pids.  release_task() therefore holds no reference to
it after dropping tasklist_lock.&lt;/p&gt;
&lt;p&gt;The other task can then remove the remaining PIDTYPE links.  Its
free_pids() call schedules delayed_put_pid(), and the RCU callback can free
the PID before the first release_task() reaches proc_flush_pid().&lt;/p&gt;
&lt;p&gt;An unprivileged reproducer races wait4(-1) against setsid() to trigger this
ordering.  Three of three fresh v7.2 KASAN boots reported:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in
    proc_invalidate_siblings_dcache+0x3e2/0x3f0
    Read of size 8 by task h7_pid_reaper/1921&lt;/p&gt;
&lt;p&gt;Call Trace:
     proc_invalidate_siblings_dcache
     release_task
     wait_consider_task
     __do_wait
     do_wait
     kernel_wait4&lt;/p&gt;
&lt;p&gt;Freed by task 0:
     kmem_cache_free
     put_pid
     delayed_put_pid
     rcu_core&lt;/p&gt;
&lt;p&gt;Last potentia…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;exit: hold a reference to thread_pid across proc_flush_pid&lt;/p&gt;
&lt;p&gt;Commit 0a36bad01731 (&amp;#34;release_task: kill the no longer needed
get/put_pid(thread_pid)&amp;#34;) removed the reference around proc_flush_pid().
It assumed that free_pids(post.pids) at the end of release_task() would
keep thread_pid alive until then.&lt;/p&gt;
&lt;p&gt;That assumption is wrong.  __change_pid() only records a detached PID in
post.pids when pid_has_task() is false for every PIDTYPE.  If another task
still uses the exiting task&amp;#39;s PID as its process group or session ID,
__unhash_process() removes the exiting task&amp;#39;s PIDTYPE_PID link but leaves
the PID out of post.pids.  release_task() therefore holds no reference to
it after dropping tasklist_lock.&lt;/p&gt;
&lt;p&gt;The other task can then remove the remaining PIDTYPE links.  Its
free_pids() call schedules delayed_put_pid(), and the RCU callback can free
the PID before the first release_task() reaches proc_flush_pid().&lt;/p&gt;
&lt;p&gt;An unprivileged reproducer races wait4(-1) against setsid() to trigger this
ordering.  Three of three fresh v7.2 KASAN boots reported:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in
    proc_invalidate_siblings_dcache+0x3e2/0x3f0
    Read of size 8 by task h7_pid_reaper/1921&lt;/p&gt;
&lt;p&gt;Call Trace:
     proc_invalidate_siblings_dcache
     release_task
     wait_consider_task
     __do_wait
     do_wait
     kernel_wait4&lt;/p&gt;
&lt;p&gt;Freed by task 0:
     kmem_cache_free
     put_pid
     delayed_put_pid
     rcu_core&lt;/p&gt;
&lt;p&gt;Last potentia…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-cpwj-27c2-jfgq</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-97903</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-97903</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: exit: hold a reference to thread_pid across proc_flush_pid Commit 0a36bad01731 (&amp;#34;release_task: kill the no longer needed get/put_pid(thread_pid)&amp;#34;) removed the reference around proc_flush_pid(). It assumed that free_pids(post.pids) at the end of release_task() would keep thread_pid alive until then. That assumption is wrong.  __change_pid() only records a detached PID in post.pids when pid_has_task() is false for every PIDTYPE.  If another task still uses the exiting task&amp;#39;s PID as its process group or session ID, __unhash_process() removes the exiting task&amp;#39;s PIDTYPE_PID link but leaves the PID out of post.pids.  release_task() therefore holds no reference to it after dropping tasklist_lock. The other task can then remove the remaining PIDTYPE links.  Its free_pids() call schedules delayed_put_pid(), and the RCU callback can free the PID before the first release_task() reaches proc_flush_pid(). An unprivileged reproducer races wait4(-1) against setsid() to trigger this ordering.  Three of three fresh v7.2 KASAN boots reported:     BUG: KASAN: slab-use-after-free in     proc_invalidate_siblings_dcache+0x3e2/0x3f0     Read of size 8 by task h7_pid_reaper/1921     Call Trace:      proc_invalidate_siblings_dcache      release_task      wait_consider_task      __do_wait      do_wait      kernel_wait4     Freed by task 0:      kmem_cache_free      put_pid      delayed_put_pid      rcu_core     Last potentially relat…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: exit: hold a reference to thread_pid across proc_flush_pid Commit 0a36bad01731 (&amp;#34;release_task: kill the no longer needed get/put_pid(thread_pid)&amp;#34;) removed the reference around proc_flush_pid(). It assumed that free_pids(post.pids) at the end of release_task() would keep thread_pid alive until then. That assumption is wrong.  __change_pid() only records a detached PID in post.pids when pid_has_task() is false for every PIDTYPE.  If another task still uses the exiting task&amp;#39;s PID as its process group or session ID, __unhash_process() removes the exiting task&amp;#39;s PIDTYPE_PID link but leaves the PID out of post.pids.  release_task() therefore holds no reference to it after dropping tasklist_lock. The other task can then remove the remaining PIDTYPE links.  Its free_pids() call schedules delayed_put_pid(), and the RCU callback can free the PID before the first release_task() reaches proc_flush_pid(). An unprivileged reproducer races wait4(-1) against setsid() to trigger this ordering.  Three of three fresh v7.2 KASAN boots reported:     BUG: KASAN: slab-use-after-free in     proc_invalidate_siblings_dcache+0x3e2/0x3f0     Read of size 8 by task h7_pid_reaper/1921     Call Trace:      proc_invalidate_siblings_dcache      release_task      wait_consider_task      __do_wait      do_wait      kernel_wait4     Freed by task 0:      kmem_cache_free      put_pid      delayed_put_pid      rcu_core     Last potentially relat…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-97903</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3579 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</guid>
    </item>
  </channel>
</rss>
