CVE-2026-99667: mm/khugepaged: always recheck the pmd in try_collapse_pte_mapped_thp()

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

mm/khugepaged: always recheck the pmd in trycollapseptemappedthp()

trycollapseptemappedthp() drops the PTE lock after it has cleared the page table, and takes the PMD lock and the PTE lock to remove it.

In between, MADVDONTNEED with CONFIGPTRECLAIM can reclaim the page table. The pmdsame() check is supposed to handle this, but it is only done with CONFIGSPLITPTEPTLOCKS.

Fix it by performing the check unconditionally.

Fix generated by an LLM and sent by Josef Bacik in private.

[ david: adjust description ]

Affected Software

4 affected componentsFixes available
linux/kernel>=6.14.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux<=7.3.4-1
6.1.176-16.1.192-26.12.107-16.12.117-17.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  3. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 6.12.107-1Fixed in 6.12.117-1Fixed in 7.3.5-1

Event History

Nov 20, 2026
CVE Published
via MITRE·05:50 AM
Data Sourced
via MITRE·05:50 AM
Description
Data Sourced
via OSV·05:50 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

What conditions are required for this race to occur?

The race requires try_collapse_pte_mapped_thp() to drop the PTE lock after clearing the page table, while MADV_DONTNEED and CONFIG_PT_RECLAIM reclaim that page table before it is removed. The vulnerable path exists because the PMD consistency check was previously limited to CONFIG_SPLIT_PTE_PTLOCKS builds.

2

Are systems without CONFIG_SPLIT_PTE_PTLOCKS affected?

Yes. The issue is that the required pmd_same() validation was performed only when CONFIG_SPLIT_PTE_PTLOCKS was enabled, even though page-table reclamation can occur during the unlocked interval. The fix makes the validation unconditional.

3

What can be done if the kernel cannot be updated immediately?

The provided information identifies CONFIG_PT_RECLAIM and MADV_DONTNEED as participating in the race, but does not provide a validated workaround or configuration mitigation. Applying a kernel release containing the referenced fixes is the documented remediation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203