{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93217 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93217 is a denial of service vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-93217 and fix it if it is affected.\n\nWhat it is: CVE-2026-93217 is a denial of service vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-93217 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-93217/ (Markdown: https://insights.sbomify.com/CVE-2026-93217/index.md)","id":"CVE-2026-93217","markdown":"https://insights.sbomify.com/CVE-2026-93217/index.md","name":"CVE-2026-93217","record":{"aliases":["DEBIAN-CVE-2026-93217","GHSA-9xmw-xhvx-px4q","UBUNTU-CVE-2026-93217"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel memory management subsystem can cause a kernel panic when device-private PMDs are encountered during madvise operations.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/madvise: skip device-private PMDs in cold and pageout walks\n\nmadvise_cold_or_pageout_pte_range() takes pmd_trans_huge_lock(), whose\npmd_is_huge() check returns true for a device-private PMD.  The subsequent\n!pmd_present() branch has a VM_BUG_ON() asserting migration is the only\nallowed non-present case; a device-private PMD trips it.\n\nSkip device-private PMDs in that non-present branch and continue to\nhuge_unlock before calling pmd_folio().  Downgrade the check to\nVM_WARN_ON_ONCE() so an unexpected PMD softleaf logs a warning rather than\npanicking.  Drop the thp_migration_supported() guard: it expands to\nIS_ENABLED(CONFIG_ARCH_SUPPORTS_PMD_SOFTLEAF), and both\npmd_is_migration_entry() and pmd_is_device_private_entry() already return\nfalse when that config is not selected, so the guard suppresses only the\ncase where the warning would already be silent.\n\nPotential trigger: an HMM-based GPU driver races with\nmadvise(MADV_COLD)/MADV_PAGEOUT: pmd_trans_huge(*pmd) reads true, then\nmigrate_vma_pages() flips the PMD to a device-private entry before the PMD\nlock is acquired.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"mm/madvise: skip device-private PMDs in cold and pageout walks","id":"CVE-2026-93217","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"mm/huge_memory: skip device-private PMDs in madvise_free_huge_pmd","id":"CVE-2026-93218"},"packages":[],"prev":{"headline":"mm/page_owner: use memcg_data snapshot to avoid TOCTOU in print_page_owner_memcg()","id":"CVE-2026-93216"},"products":["Linux"],"published":"2026-09-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A race condition in the Linux kernel memory management subsystem can cause a kernel panic when device-private PMDs are encountered during madvise operations.","url":"https://insights.sbomify.com/CVE-2026-93217/"}