CVE-2026-99530: cgroup: serialize migrations of newly forked processes
In the Linux kernel, the following vulnerability has been resolved:
cgroup: serialize migrations of newly forked processes
With favordynmods enabled, a cgroup.procs migration takes the target threadgroup's cgroupthreadgrouprwsem for writing. A process fork holds the forking threadgroup's semaphore for reading. These are different semaphores when fork creates a new process.
copyprocess() publishes the child's PID before cgrouppostfork() links the child to its cssset. A writer can find the child in that interval, take its uncontended semaphore, and migrate it while child->cgroups still points to initcssset and child->cglist is empty. Migration links the node into initcssset.mgtasks. cgrouppostfork() then adds the same node to the intended cssset as though it were unlinked, corrupting both task lists and their cssset ownership.
This regresses the fork/migration race fixed by commit b12b533fa523 ("cgroups: add lock for child->cgroups in cgrouppostfork()") and restored again in 2012 after the lock had been removed. The old tasklock protection was later superseded by global cssset and cgroup threadgroup locking. The change identified by the Fixes tag narrowed only the migration side back to a per-threadgroup lock, recreating the different-process exclusion failure.
Take the new threadgroup's semaphore for reading before the child becomes visible and hold it through cgrouppostfork(). Use a nested lock subclass because fork already holds the parent's semaphore. CLONETHREAD children share the parent's signalstruct and remain covered by the existing lock. Migrations of unrelated, fully initialized threadgroups remain concurrent.
An AI coding assistant was used to identify and reproduce the regression and to develop and test this fix.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.61 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.2