CVE-2026-99530
Severity unknownNo known exploitationFix availablecgroup: serialize migrations of newly forked processes
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 6% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
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 cgroup_threadgroup_rwsem for writing. A process fork holds the forking threadgroup's semaphore for reading. These are different semaphores when fork creates a new process. copy_process() publishes the child's PID before cgroup_post_fork() links the child to its css_set. A writer can find the child in that interval, take its uncontended semaphore, and migrate it while child->cgroups still points to init_css_set and child->cg_list is empty. Migration links the node into init_css_set.mg_tasks. cgroup_post_fork() then adds the same node to the intended css_set as though it were unlinked, corrupting both task lists and their css_set ownership. This regresses the fork/migration race fixed by commit b12b533fa523 ("cgroups: add lock for child->cgroups in cgroup_post_fork()") and restored again in 2012 after the lock had been removed. The old task_lock protection was later superseded by global css_set 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 cgroup_post_fork(). Use a nested lock subclass because fork already holds the parent's semaphore. CLONE_THREAD children share the parent's signal_struct 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.
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Linux))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 0568f89d4fb82d98001baeb870e92f43cd1f7317 before 13610241843ccd928d83c6d51b5e044e4faf56c8 | 13610241843ccd928d83c6d51b5e044e4faf56c8 | CVE Program |
| Linux | Linux | from 0568f89d4fb82d98001baeb870e92f43cd1f7317 before bf6fbf46b5ff68c4eebad5aa52309eb124f4509c | bf6fbf46b5ff68c4eebad5aa52309eb124f4509c | CVE Program |
| Linux | Linux | from 0568f89d4fb82d98001baeb870e92f43cd1f7317 before d3d5560fb7550e74fb9851826d7dab505ffd05e0 | d3d5560fb7550e74fb9851826d7dab505ffd05e0 | CVE Program |
| Linux | Linux | 6.18 | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.61 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.3.2 up to and including 7.3.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.4-rc1 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 6.18 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Linux)