CVE-2026-46017
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. [[email protected]: move the comment]
How to fix
- linux linux_kernel7.0.4 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| linux linux_kernel | v < 7.0.4 | 7.0.4 |
| microsoft azl3_kernel_6.6.139.1-1 | No range specified | — |
| microsoft azl3_kernel_6.6.145.2-1 | No range specified | — |
| microsoft azl3_kernel_6.6.152.1-1 | No range specified | — |
| microsoft azl3_kernel_6.6.141.1-1 | No range specified | — |
| microsoft azl3_kernel_6.6.143.1-1 | No range specified | — |
| microsoft azl3_kernel_6.6.144.1-1 | No range specified | — |
| microsoft azl3_kernel_6.6.150.1-1 | No range specified | — |
| microsoft azl3_kernel_6.6.157.1-1 | No range specified | — |
| microsoft azl3_kernel_6.6.159.1-1 | No range specified | — |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.