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

CVE record · `CVE-2026-72010`

- **Identifiers:** `CVE-2026-72010`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 15 Aug 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 15 Aug 2026, 05:51 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `ae1c802382f7af60aa54879fb4f5920a9df1ff48 to before b7adeba2a21c98c7b20f18e27e3ead86bdb5e08d` (git)
  - affected: `ae1c802382f7af60aa54879fb4f5920a9df1ff48 to before fcc8c310539c3cc523419113b227161a96b50550` (git)
  - affected: `ae1c802382f7af60aa54879fb4f5920a9df1ff48 to before 4b06449384b9ee5b3372bab60601ba5cd4162086` (git)
  - affected: `ae1c802382f7af60aa54879fb4f5920a9df1ff48 to before 02f67c4f88be8e3dbd91951d13cdcc5bcc82e9c7` (git)
  - affected: `ae1c802382f7af60aa54879fb4f5920a9df1ff48 to before fc680afc510157f6b137956011c09abc23eb0842` (git)
  - affected: `ae1c802382f7af60aa54879fb4f5920a9df1ff48 to before c844b7d9a9586de15dd28c06da5cc7f6ab28787d` (git)
  - affected: `ae1c802382f7af60aa54879fb4f5920a9df1ff48 to before c17f06d8a085d6be58b544a440ce243f5e441a60` (git)
  - affected: `ae1c802382f7af60aa54879fb4f5920a9df1ff48 to before b983c56426383e4a06fa5970c4e33cee879b1482` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `3.17`
  - unaffected: `before 3.17` (semver)
  - unaffected: `5.10.261 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.212 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.178 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.145 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.97 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.40 to 6.18.*, inclusive` (semver)
  - unaffected: `7.1.5 to 7.1.*, inclusive` (semver)
  - unaffected: `7.2 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0022, the 12th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 15 Aug 2026, 05:51 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-72010)
- 15 Aug 2026, 06:20 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-72010)

## Sources

- [CVE List: CVE-2026-72010](https://www.cve.org/CVERecord?id=CVE-2026-72010)
- [NVD: CVE-2026-72010](https://nvd.nist.gov/vuln/detail/CVE-2026-72010)

### References from the CNA

- <https://git.kernel.org/stable/c/b7adeba2a21c98c7b20f18e27e3ead86bdb5e08d>
- <https://git.kernel.org/stable/c/fcc8c310539c3cc523419113b227161a96b50550>
- <https://git.kernel.org/stable/c/4b06449384b9ee5b3372bab60601ba5cd4162086>
- <https://git.kernel.org/stable/c/02f67c4f88be8e3dbd91951d13cdcc5bcc82e9c7>
- <https://git.kernel.org/stable/c/fc680afc510157f6b137956011c09abc23eb0842>
- <https://git.kernel.org/stable/c/c844b7d9a9586de15dd28c06da5cc7f6ab28787d>
- <https://git.kernel.org/stable/c/c17f06d8a085d6be58b544a440ce243f5e441a60>
- <https://git.kernel.org/stable/c/b983c56426383e4a06fa5970c4e33cee879b1482>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-72010>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-72010/>. Everything for agents: <https://agentprime.io/llms.txt>.
