CVE-2026-72010

CVE CVE-2026-72010EUVD EUVD-2026-59109Published 2026-08-15T05:51:39.000ZLast changed 2026-08-17T05:06:32.000Z

What the advisory describes

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 ]

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux ae1c802382f7af60aa54879fb4f5920a9df1ff48 <b7adeba2a21c98c7b20f18e27e3ead86bdb5e08d; patch: 5.15.212; patch: 7.1.5; patch: 6.12.97; patch: 7.2; ae1c802382f7af60aa54879fb4f5920a9df1ff48 <c17f06d8a085d6be58b544a440ce243f5e441a60; patch: 5.10.261; ae1c802382f7af60aa54879fb4f5920a9df1ff48 <fcc8c310539c3cc523419113b227161a96b50550; patch: 6.6.145; ae1c802382f7af60aa54879fb4f5920a9df1ff48 <02f67c4f88be8e3dbd91951d13cdcc5bcc82e9c7; 3.17; ae1c802382f7af60aa54879fb4f5920a9df1ff48 <fc680afc510157f6b137956011c09abc23eb0842; ae1c802382f7af60aa54879fb4f5920a9df1ff48 <4b06449384b9ee5b3372bab60601ba5cd4162086; ae1c802382f7af60aa54879fb4f5920a9df1ff48 <b983c56426383e4a06fa5970c4e33cee879b1482; patch: 6.18.40; ae1c802382f7af60aa54879fb4f5920a9df1ff48 <c844b7d9a9586de15dd28c06da5cc7f6ab28787d; patch: 0; patch: 6.1.178

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.