CVE-2026-72010

cgroup/cpuset: rebind mm mempolicy to effective_mems, not mems_allowed

N/A
Published: August 15, 2026 at 05:51 AM UTC
Updated: August 17, 2026 at 06:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: cgroup/cpuset: rebind mm mempolicy to effective_mems, not mems_allowed Creating a child cpuset where cpuset.mems is never set leads to a div/0 when a VMA mempolicy with MPOL_F_RELATIVE_NODES rebinds in response to a CPU hotplug event. Reproduction steps: 1) Create a cgroup w/ cpuset controls (do not set cpuset.mems) 2) Move the task into the child cpuset 3) Create a VMA mempolicy for that task with MPOL_F_RELATIVE_NODES 4) unplug and hotplug a cpu echo 0 > /sys/devices/system/cpu/cpu1/online echo 1 > /sys/devices/system/cpu/cpu1/online 5) mempolicy rebind does a div/0 in mpol_relative_nodemask on the call to __nodes_fold() The cpuset code passes (cs->mems_allowed) which is not guaranteed to have nodes to the rebind routine. Use cs->effective_mems instead, which is guaranteed to have a non-empty nodemask once we reach that code path. [ david: add a comment, slightly rephrase description ]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.17 ≤ v < 5.10.2613.17 ≤ v < 5.15.2123.17 ≤ v < 6.1.1783.17 ≤ v < 6.12.973.17 ≤ v < 6.18.403.17 ≤ v < 6.6.1453.17 ≤ v < 7.1.53.17 ≤ v < 7.23.17ae1c802382f7af60aa54879fb4f5920a9df1ff48
Vendor states this is fixed in 02f67c4f88be8e3dbd91951d13cdcc5bcc82e9c7 (fixed)
Vendor states this is fixed in 4b06449384b9ee5b3372bab60601ba5cd4162086 (fixed)
Vendor states this is fixed in b7adeba2a21c98c7b20f18e27e3ead86bdb5e08d (fixed)
Vendor states this is fixed in b983c56426383e4a06fa5970c4e33cee879b1482 (fixed)
Vendor states this is fixed in c17f06d8a085d6be58b544a440ce243f5e441a60 (fixed)
Vendor states this is fixed in c844b7d9a9586de15dd28c06da5cc7f6ab28787d (fixed)
Vendor states this is fixed in fc680afc510157f6b137956011c09abc23eb0842 (fixed)
Vendor states this is fixed in fcc8c310539c3cc523419113b227161a96b50550 (fixed)
Vendor states this is fixed in 3.17 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card