# mm: fix deferred split queue races during migration

CVE record · `CVE-2026-46017`

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

Published by the CVE Program (CNA: Linux) at 27 May 2026, 12:56 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: `1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before cbf75cf212ee6e499abc1757fb4b5ae6d70ed0aa` (git)
  - affected: `1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before 3bac01168982ec3e3bf87efdc1807c7933590a85` (git)
  - affected: `before 7.0.4` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - unaffected: `7.0.4 to 7.0.*, inclusive` (semver)
  - unaffected: `7.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Linux kernel versions before 7.0.4 are affected, along with certain earlier commit ranges, by a race in the memory management deferred split queue during folio migration. The source gives few details about the attack path, but the flaw can cause a warning to trigger and a folio to be silently dropped from the split queue. Upgrade to Linux 7.0.4 or later in the 7.0 series, or to 7.1 or later. The source lists no workaround.

Written 17 Nov 2026.

## 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.0010, the 1st percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 27 May 2026, 12:56 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-46017)
- 27 May 2026, 14:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-46017)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/cbf75cf212ee6e499abc1757fb4b5ae6d70ed0aa>
- <https://git.kernel.org/stable/c/3bac01168982ec3e3bf87efdc1807c7933590a85>

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-46017>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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