cgroup/cpuset: rebind mm mempolicy to effective_mems, not mems_allowed
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel fcc8c310539c3cc523419113b227161a96b50550, Kernel 02f67c4f88be8e3dbd91951d13cdcc5bcc82e9c7, Kernel 4b06449384b9ee5b3372bab60601ba5cd4162086 and 12 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=ae1c802382f7af60aa54879fb4f5920a9df1ff48 <fcc8c310539c3cc523419113b227161a96b50550, >=ae1c802382f7af60aa54879fb4f5920a9df1ff48 <02f67c4f88be8e3dbd91951d13cdcc5bcc82e9c7, >=ae1c802382f7af60aa54879fb4f5920a9df1ff48 <4b06449384b9ee5b3372bab60601ba5cd4162086, >=ae1c802382f7af60aa54879fb4f5920a9df1ff48 <b7adeba2a21c98c7b20f18e27e3ead86bdb5e08d, >=ae1c802382f7af60aa54879fb4f5920a9df1ff48 <b983c56426383e4a06fa5970c4e33cee879b1482, >=ae1c802382f7af60aa54879fb4f5920a9df1ff48 <c17f06d8a085d6be58b544a440ce243f5e441a60, >=ae1c802382f7af60aa54879fb4f5920a9df1ff48 <c844b7d9a9586de15dd28c06da5cc7f6ab28787d, >=ae1c802382f7af60aa54879fb4f5920a9df1ff48 <fc680afc510157f6b137956011c09abc23eb0842, =3.17 | fcc8c310539c3cc523419113b227161a96b50550, 02f67c4f88be8e3dbd91951d13cdcc5bcc82e9c7, 4b06449384b9ee5b3372bab60601ba5cd4162086, b7adeba2a21c98c7b20f18e27e3ead86bdb5e08d, b983c56426383e4a06fa5970c4e33cee879b1482, c17f06d8a085d6be58b544a440ce243f5e441a60, c844b7d9a9586de15dd28c06da5cc7f6ab28787d, fc680afc510157f6b137956011c09abc23eb0842 |
| linux-kernel: Kernel | >=5.11.0 <5.15.212, >=5.16.0 <6.1.178, >=6.13.0 <6.18.40, >=6.19.0 <7.1.5, >=6.2.0 <6.6.145, >=6.7.0 <6.12.97, >=3.17.0 <5.10.261 | 5.15.212, 6.1.178, 6.18.40, 7.1.5, 6.6.145, 6.12.97, 5.10.261 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket