<?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, 06 Oct 2026 03:10:01 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43439 — cgroup: fix race between task migration and iteration</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43439</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;cgroup: fix race between task migration and iteration&lt;/p&gt;
&lt;p&gt;When a task is migrated out of a css_set, cgroup_migrate_add_task()
first moves it from cset-&amp;gt;tasks to cset-&amp;gt;mg_tasks via:&lt;/p&gt;
&lt;p&gt;list_move_tail(&amp;amp;task-&amp;gt;cg_list, &amp;amp;cset-&amp;gt;mg_tasks);&lt;/p&gt;
&lt;p&gt;If a css_task_iter currently has it-&amp;gt;task_pos pointing to this task,
css_set_move_task() calls css_task_iter_skip() to keep the iterator
valid. However, since the task has already been moved to -&amp;gt;mg_tasks,
the iterator is advanced relative to the mg_tasks list instead of the
original tasks list. As a result, remaining tasks on cset-&amp;gt;tasks, as
well as tasks queued on cset-&amp;gt;mg_tasks, can be skipped by iteration.&lt;/p&gt;
&lt;p&gt;Fix this by calling css_set_skip_task_iters() before unlinking
task-&amp;gt;cg_list from cset-&amp;gt;tasks. This advances all active iterators to
the next task on cset-&amp;gt;tasks, so iteration continues correctly even
when a task is concurrently being migrated.&lt;/p&gt;
&lt;p&gt;This race is hard to hit in practice without instrumentation, but it
can be reproduced by artificially slowing down cgroup_procs_show().
For example, on an Android device a temporary
/sys/kernel/cgroup/cgroup_test knob can be added to inject a delay
into cgroup_procs_show(), and then:&lt;/p&gt;
&lt;p&gt;1) Spawn three long-running tasks (PIDs 101, 102, 103).
  2) Create a test cgroup and move the tasks into it.
  3) Enable a large delay via /sys/kernel/cgroup/cgroup_test.
  4) In one shell, read cgroup.procs from the test cgroup.
  5) Within the…&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;cgroup: fix race between task migration and iteration&lt;/p&gt;
&lt;p&gt;When a task is migrated out of a css_set, cgroup_migrate_add_task()
first moves it from cset-&amp;gt;tasks to cset-&amp;gt;mg_tasks via:&lt;/p&gt;
&lt;p&gt;list_move_tail(&amp;amp;task-&amp;gt;cg_list, &amp;amp;cset-&amp;gt;mg_tasks);&lt;/p&gt;
&lt;p&gt;If a css_task_iter currently has it-&amp;gt;task_pos pointing to this task,
css_set_move_task() calls css_task_iter_skip() to keep the iterator
valid. However, since the task has already been moved to -&amp;gt;mg_tasks,
the iterator is advanced relative to the mg_tasks list instead of the
original tasks list. As a result, remaining tasks on cset-&amp;gt;tasks, as
well as tasks queued on cset-&amp;gt;mg_tasks, can be skipped by iteration.&lt;/p&gt;
&lt;p&gt;Fix this by calling css_set_skip_task_iters() before unlinking
task-&amp;gt;cg_list from cset-&amp;gt;tasks. This advances all active iterators to
the next task on cset-&amp;gt;tasks, so iteration continues correctly even
when a task is concurrently being migrated.&lt;/p&gt;
&lt;p&gt;This race is hard to hit in practice without instrumentation, but it
can be reproduced by artificially slowing down cgroup_procs_show().
For example, on an Android device a temporary
/sys/kernel/cgroup/cgroup_test knob can be added to inject a delay
into cgroup_procs_show(), and then:&lt;/p&gt;
&lt;p&gt;1) Spawn three long-running tasks (PIDs 101, 102, 103).
  2) Create a test cgroup and move the tasks into it.
  3) Enable a large delay via /sys/kernel/cgroup/cgroup_test.
  4) In one shell, read cgroup.procs from the test cgroup.
  5) Within the…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43439</guid>
    </item>
  </channel>
</rss>
