Skip to main content
VulnerabilityPublished Updated

CVE-2026-46017: Linux kernel · mm: fix deferred split queue races during migration

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in cbf75cf212ee6e499abc1757fb4b5ae6d70ed0aa : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:34 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in cbf75cf212ee6e499abc1757fb4b5ae6d70ed0aa, 7.0.4, 3bac01168982ec3e3bf87efdc1807c7933590a85

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade Linux kernel to cbf75cf212ee6e499abc1757fb4b5ae6d70ed0aa, 7.0.4 or 3bac01168982ec3e3bf87efdc1807c7933590a85.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • <7.0.4
Fixed in
  • cbf75cf212ee6e499abc1757fb4b5ae6d70ed0aa
  • 7.0.4
  • 3bac01168982ec3e3bf87efdc1807c7933590a85

Description

In the Linux kernel, the following vulnerability has been resolved: mm: fix deferred split queue races during migration migrate_folio_move() records the deferred split queue state from src and replays it on dst. Replaying it after remove_migration_ptes(src, dst, 0) makes dst visible before it is requeued, so a concurrent rmap-removal path can mark dst partially mapped and trip the WARN in deferred_split_folio(). Move the requeue before remove_migration_ptes() so dst is back on the deferred split queue before it becomes visible again. Because migration still holds dst locked at that point, teach deferred_split_scan() to requeue a folio when folio_trylock() fails. Otherwise a fully mapped underused folio can be dequeued by the shrinker and silently lost from split_queue. [ziy@nvidia.com: move the comment]

References

Community reviews

Loading reviews…