{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-99650","id":"CVE-2026-99650","title":"Linux kernel use-after-free in KSM swap-in","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/ksm: fix use of a freed anon_vma at swap-in\n\nA folio read from a swap slot previously shared by KSM can remain in the\nswap cache after the process that first mapped it exits. Its anon_vma\ncan then be freed, so ksm_might_need_to_copy() must not dereference it\nto compare roots.\n\nDoing so can result in some false-positives, resul","descriptionLong":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/ksm: fix use of a freed anon_vma at swap-in\n\nA folio read from a swap slot previously shared by KSM can remain in the\nswap cache after the process that first mapped it exits. Its anon_vma\ncan then be freed, so ksm_might_need_to_copy() must not dereference it\nto compare roots.\n\nDoing so can result in some false-positives, resulting in the reverse\nmapping missing the new folio mapping, preventing migration and reclaim.\n\nSLAB_TYPESAFE_BY_RCU allows individual anon_vma objects to be reused\nimmediately after freeing. A stale pointer can then refer to another\nanon_vma whose root matches, even though the target VMA is not linked\nto that anon_vma.\n\nMove the anonymous rmap compatibility checks into\nfolio_anon_rmap_compatible(). Keep the page-index check and compare the\nfolio's anon_vma pointer against the VMA's own anon_vma and root first.\n\nIf neither matches, bite the bullet and walk the VMA's anon_vma_chain.\nThe VMA keeps these anon_vmas alive, and finding a match guarantees that\nreverse mapping can find the new mapping.\n\nLorenzo Stoakes says in a private discussion:\n\n  \"This isn't quite equivalent to the existing check.\n\n  Every anon_vma in an anon_vma_chain shares the same root, but if you\n  split a VMA then fork both of them like this:\n\n                  VMA A\n               /        \\         <split>\n            VMA B      VMA C\n               \\        /\n        root <- anon_vma 1\n               ----^ ^----        <fork>\n              /   parent  \\\n        anon_vma 2   anon_vma 3\n             |            |\n           VMA D        VMA E\n\n  VMA's D and E both get their own new\n  anon_vma's such that:\n\n  VMA D: anon_vma 2 -> anon_vma 1 -> root\n  VMA E: anon_vma 3 -> anon_vma 1 -> root\n\n  And if you found a folio referencing anon_vma 2, the existing check:\n\n\tanon_vma->root == vma->anon-vma->root\n\n  Would be true for VMA's B, C, D & E.\n\n  However after your change it'd be true for VMA D only, as it's the only\n  one with anon_vma 2 in its anon_vma_chain.\n\n  Whether or not that could actually happen in practice... 🙂 I don't\n  know.\n\n  [...] after your change it'd be true for VMA D only, as it's the only\n  one with anon_vma 2 in its anon_vma_chain. [...] I would [...] say that\n  you are making the test stricter but more correct.\n\"\n\nIf this affects performance when KSM was never even involved, we could\njust track whether KSM ever merged anything and just skip these checks.\n\nThere isn't really a lot we can do otherwise: for mapped folios we might\nbe able to use folio_get_anon_vma(), but for unmapped folios there really\nis no easy way to see if the anon_vma is still valid.\n\nDocument the (confusing) lifetime requirements of folio_anon_vma().","published":"2026-11-20T05:50:03.838Z","updated":"2026-11-20T05:50:03.838Z","reserved":"2026-09-25T10:25:14.427Z","status":"PUBLISHED","rejected":false,"assigner":"Linux","metric":null,"metrics":[],"rating":"unrated","products":["Linux"],"affectedProducts":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"ba6f0ff3981e6263ab81ac512f04cca55b85ec81","lessThan":"85260730efefc48111603fa865d224bae1f5447a","status":"affected","versionType":"git"},{"version":"ba6f0ff3981e6263ab81ac512f04cca55b85ec81","lessThan":"4c2dec1dce368ad9e9b1814307cb5ef3832fa07e","status":"affected","versionType":"git"}],"platforms":[]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"2.6.36","status":"affected"},{"version":"0","lessThan":"2.6.36","status":"unaffected","versionType":"semver"},{"version":"7.3.5","lessThanOrEqual":"7.3.*","status":"unaffected","versionType":"semver"},{"version":"7.4-rc2","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}],"platforms":[]}],"packages":[],"cwes":[],"aliases":[],"references":[{"url":"https://git.kernel.org/stable/c/85260730efefc48111603fa865d224bae1f5447a","tags":[]},{"url":"https://git.kernel.org/stable/c/4c2dec1dce368ad9e9b1814307cb5ef3832fa07e","tags":[]}],"patchReferenced":false,"fixAvailable":false,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":null,"epss":null,"epssPercentile":null,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-99650","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99650","ok":false,"note":"not found"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-99650","ok":false,"note":"no open-source package data"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-99650","ok":false,"note":"no score yet"}],"aiTitle":true,"tech":[],"critical":[],"attention":null}