{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93075 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93075 is an use after free vulnerability in Linux, published on 17 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-93075 and fix it if it is affected.\n\nWhat it is: CVE-2026-93075 is an use after free vulnerability in Linux, published on 17 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-93075 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-93075/ (Markdown: https://insights.sbomify.com/CVE-2026-93075/index.md)","id":"CVE-2026-93075","markdown":"https://insights.sbomify.com/CVE-2026-93075/index.md","name":"CVE-2026-93075","record":{"aliases":["DEBIAN-CVE-2026-93075","GHSA-m6jw-vjqw-78fh","UBUNTU-CVE-2026-93075"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"A use-after-free vulnerability in the Linux kernel DAX fsdev driver allows local attackers to execute arbitrary code or cause a denial of service via stale pointers after device unbind.","user_interaction":"not_required","vuln_class":"use_after_free"},"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\ndax/fsdev: clear pgmap ops and owner on unbind\n\nfsdev_dax_probe() sets pgmap-\u003eops = \u0026fsdev_pagemap_ops and\npgmap-\u003eowner = dev_dax, but nothing ever clears them. For a dynamic\ndevice the pgmap is devm-allocated and freed on unbind, so this is\nharmless. For a static device the pgmap is the shared, long-lived one\nowned by the dax bus (kill_dev_dax() only NULLs dev_dax-\u003epgmap for the\nnon-static case), and device.c's probe sets only pgmap-\u003etype, never\nclearing ops/owner.\n\nSo after fsdev unbinds a static device the stale fsdev_pagemap_ops\nsurvives on the shared pgmap. If the device is then rebound to\ndevice_dax (MEMORY_DEVICE_GENERIC, which installs no -\u003ememory_failure),\nor the fsdev_dax module is unloaded, a subsequent memory_failure on that\npgmap dispatches through the stale -- and possibly freed -- handler.\n\nRegister a devm action that clears pgmap-\u003eops and pgmap-\u003eowner on unbind,\nsymmetric with setting them at probe, so the pgmap carries no fsdev state\nonce fsdev is detached.","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":"dax/fsdev: clear pgmap ops and owner on unbind","id":"CVE-2026-93075","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"dax/fsdev: clear vmemmap_shift when binding static pgmap","id":"CVE-2026-93076"},"packages":[],"prev":{"headline":"dax/fsdev: use __va(phys) for kaddr in direct_access","id":"CVE-2026-93074"},"products":["Linux"],"published":"2026-09-17","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 use-after-free vulnerability in the Linux kernel DAX fsdev driver allows local attackers to execute arbitrary code or cause a denial of service via stale pointers after device unbind.","url":"https://insights.sbomify.com/CVE-2026-93075/"}