CVE Catalog

CVE-2026-93218

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel's mm/huge_memory, madvise_free_huge_pmd() can encounter a device-private PMD and enter the !pmd_present() branch, leading to pmd_folio() being called on an unexpected PMD. This can occur when an HMM-based GPU driver races with madvise(MADV_FREE).

Risk Assessment

This can cause a kernel panic or memory corruption, posing a denial of service (DoS) and system instability risk.

Recommendation

Update the Linux kernel to a version containing the fix that skips device-private PMDs and downgrades the check to VM_WARN_ON_ONCE().

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: mm/huge_memory: skip device-private PMDs in madvise_free_huge_pmd madvise_free_pte_range() checks pmd_trans_huge(*pmd) unlocked, then madvise_free_huge_pmd() takes pmd_trans_huge_lock(). pmd_is_huge() returns true for a device-private PMD, so orig_pmd can be device-private and enter the !pmd_present() branch. Skip device-private PMDs in that non-present branch and continue to out before calling pmd_folio(). Downgrade the check to VM_WARN_ON_ONCE() so an unexpected PMD softleaf logs a warning rather than panicking. Drop the thp_migration_supported() guard: it expands to IS_ENABLED(CONFIG_ARCH_SUPPORTS_PMD_SOFTLEAF), and both pmd_is_migration_entry() and pmd_is_device_private_entry() already return false when that config is not selected, so the guard suppresses only the case where the warning would already be silent. Potential trigger: an HMM-based GPU driver races with madvise(MADV_FREE): migrate_vma_pages() flips the PMD to a device-private entry between the caller's pmd_trans_huge() check and the callee's pmd_trans_huge_lock().

Vulnerability data from NVD (NIST) · CISA KEV · EPSS