# CVE-2026-43439: cgroup: fix race between task migration and iteration

Status: published. Published: 2026-05-08. Updated: 2026-11-06.

In the Linux kernel, the following vulnerability has been resolved:

cgroup: fix race between task migration and iteration

When a task is migrated out of a css_set, cgroup_migrate_add_task()
first moves it from cset->tasks to cset->mg_tasks via:

    list_move_tail(&task->cg_list, &cset->mg_tasks);

If a css_task_iter currently has it->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 ->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->tasks, as
well as tasks queued on cset->mg_tasks, can be skipped by iteration.

Fix this by calling css_set_skip_task_iters() before unlinking
task->cg_list from cset->tasks. This advances all active iterators to
the next task on cset->tasks, so iteration continues correctly even
when a task is concurrently being migrated.

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:

  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 delay window, in another shell migrate PID 102 by
     writing it to a different cgroup.procs file.

Under this setup, cgroup.procs can intermittently show only PID 101
while skipping PID 103. Once the migration completes, reading the
file again shows all tasks as expected.

Note that this change does not allow removing the existing
css_set_skip_task_iters() call in css_set_move_task(). The new call
in cgroup_migrate_add_task() only handles iterators that are racing
with migration while the task is still on cset->tasks. Iterators may
also start after the task has been moved to cset->mg_tasks. If we
dropped css_set_skip_task_iters() from css_set_move_task(), such
iterators could keep task_pos pointing to a migrating task, causing
css_task_iter_advance() to malfunction on the destination css_set,
up to and including crashes or infinite loops.

The race window between migration and iteration is very small, and
css_task_iter is not on a hot path. In the worst case, when an
iterator is positioned on the first thread of the migrating process,
cgroup_migrate_add_task() may have to skip multiple tasks via
css_set_skip_task_iters(). However, this only happens when migration
and iteration actually race, so the performance impact is negligible
compared to the correctness fix provided here.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ b636fd38dc40113f853337a7d2a6885ad23b8811; < 7c85debc35e6d131bd29c64f2ae78c6ede0e55c4 (affected, git); ≥ b636fd38dc40113f853337a7d2a6885ad23b8811; < 3b95abab7369235a37b15eaec6e1a0b443bba7c7 (affected, git); ≥ b636fd38dc40113f853337a7d2a6885ad23b8811; < 4a9654a2b46cfdaae287fb8995f536245635e467 (affected, git); ≥ b636fd38dc40113f853337a7d2a6885ad23b8811; < 3dfd1328c05234e8d8fa61948b2ba82680594988 (affected, git); ≥ b636fd38dc40113f853337a7d2a6885ad23b8811; < 9cca530c7cc1b3e02cb8fa7f80060dd4b38562ce (affected, git); ≥ b636fd38dc40113f853337a7d2a6885ad23b8811; < 86ceaccfdfa16dad05addb33dc206e03589bcfd1 (affected, git); ≥ b636fd38dc40113f853337a7d2a6885ad23b8811; < 9dc76f6fc0d28d2382583715bc4ec22f28104845 (affected, git); ≥ b636fd38dc40113f853337a7d2a6885ad23b8811; < 5ee01f1a7343d6a3547b6802ca2d4cdce0edacb1 (affected, git); b0af004fd58ded5f898630db008c5b824c27d7db (affected, git); 370b9e6399da09fe10005fe455878b356de7b85f (affected, git); ≥ 4.14.138; < 4.15 (affected, semver); ≥ 4.19.66; < 4.20 (affected, semver). Source: CNA: Linux
- Linux / Linux: 5.2 (affected); ≥ 0; < 5.2 (unaffected, semver); ≥ 5.10.253; ≤ 5.10.* (unaffected, semver); ≥ 5.15.203; ≤ 5.15.* (unaffected, semver); ≥ 6.1.167; ≤ 6.1.* (unaffected, semver); ≥ 6.6.130; ≤ 6.6.* (unaffected, semver); ≥ 6.12.78; ≤ 6.12.* (unaffected, semver); ≥ 6.18.19; ≤ 6.18.* (unaffected, semver); ≥ 6.19.9; ≤ 6.19.* (unaffected, semver); ≥ 7.0; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: 0.09% as of 2026-11-06; percentile 0.41%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/7c85debc35e6d131bd29c64f2ae78c6ede0e55c4 (CNA: Linux)

- https://git.kernel.org/stable/c/3b95abab7369235a37b15eaec6e1a0b443bba7c7 (CNA: Linux)

- https://git.kernel.org/stable/c/4a9654a2b46cfdaae287fb8995f536245635e467 (CNA: Linux)

- https://git.kernel.org/stable/c/3dfd1328c05234e8d8fa61948b2ba82680594988 (CNA: Linux)

- https://git.kernel.org/stable/c/9cca530c7cc1b3e02cb8fa7f80060dd4b38562ce (CNA: Linux)

- https://git.kernel.org/stable/c/86ceaccfdfa16dad05addb33dc206e03589bcfd1 (CNA: Linux)

- https://git.kernel.org/stable/c/9dc76f6fc0d28d2382583715bc4ec22f28104845 (CNA: Linux)

- https://git.kernel.org/stable/c/5ee01f1a7343d6a3547b6802ca2d4cdce0edacb1 (CNA: Linux)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-43439; retrieved 2026-11-06; source updated 2026-11-06

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-43439; retrieved 2026-11-06; source updated Not reported

Revision: c6e492d5de16f6a22aaa50540acc192aa48048f51f15ab826f89da813df6cd64

Canonical: https://y2.dev/cve/CVE-2026-43439

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.