CVE-2026-93218
Last modified
CVE-2026-93218 is a vulnerability of currently unknown severity. 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().
Description
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().
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 368076f52ebeecd33e10a9f80905d7508b6b6149, < 5e3026bf736498115884d6c7bd0308ba29e0474c; >= 368076f52ebeecd33e10a9f80905d7508b6b6149, < ce579dcf730ce5ed8043a5eeea18a3e6706a97e5 |
| Linux | Linux | 6.19 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-93218?
How severe is CVE-2026-93218?
How do I fix CVE-2026-93218?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-93212In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93213In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93214In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93215In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93216In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93217In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93219In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9322IBM WebSphere Application Server 9.0, and 8.5 and IBM WebSph…7.5
- CVE-2026-93220In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93221In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93222In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93223In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-93218?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
