AZL-115447: CVE-2026-99650 affecting package kernel 6.6.161.1-1
In the Linux kernel, the following vulnerability has been resolved:
mm/ksm: fix use of a freed anonvma at swap-in
A folio read from a swap slot previously shared by KSM can remain in the swap cache after the process that first mapped it exits. Its anonvma can then be freed, so ksmmightneedtocopy() must not dereference it to compare roots.
Doing so can result in some false-positives, resulting in the reverse mapping missing the new folio mapping, preventing migration and reclaim.
SLABTYPESAFEBYRCU allows individual anonvma objects to be reused immediately after freeing. A stale pointer can then refer to another anonvma whose root matches, even though the target VMA is not linked to that anonvma.
Move the anonymous rmap compatibility checks into folioanonrmapcompatible(). Keep the page-index check and compare the folio's anonvma pointer against the VMA's own anonvma and root first.
If neither matches, bite the bullet and walk the VMA's anonvmachain. The VMA keeps these anonvmas alive, and finding a match guarantees that reverse mapping can find the new mapping.
Lorenzo Stoakes says in a private discussion:
"This isn't quite equivalent to the existing check.
Every anonvma in an anonvmachain shares the same root, but if you split a VMA then fork both of them like this:
VMA A / \ <split> VMA B VMA C \ / root <- anonvma 1 ----^ ^---- <fork> / parent \ anonvma 2 anonvma 3 | | VMA D VMA E
VMA's D and E both get their own new anonvma's such that:
VMA D: anonvma 2 -> anonvma 1 -> root VMA E: anonvma 3 -> anonvma 1 -> root
And if you found a folio referencing anonvma 2, the existing check:
anonvma->root == vma->anon-vma->root
Would be true for VMA's B, C, D & E.
However after your change it'd be true for VMA D only, as it's the only one with anonvma 2 in its anonvmachain.
Whether or not that could actually happen in practice... 🙂 I don't know.
[...] after your change it'd be true for VMA D only, as it's the only one with anonvma 2 in its anonvmachain. [...] I would [...] say that you are making the test stricter but more correct. "
If this affects performance when KSM was never even involved, we could just track whether KSM ever merged anything and just skip these checks.
There isn't really a lot we can do otherwise: for mapped folios we might be able to use foliogetanonvma(), but for unmapped folios there really is no easy way to see if the anonvma is still valid.
Document the (confusing) lifetime requirements of folioanonvma().