{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93076 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93076 is a 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-93076 and fix it if it is affected.\n\nWhat it is: CVE-2026-93076 is a 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-93076 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-93076/ (Markdown: https://insights.sbomify.com/CVE-2026-93076/index.md)","id":"CVE-2026-93076","markdown":"https://insights.sbomify.com/CVE-2026-93076/index.md","name":"CVE-2026-93076","record":{"aliases":["DEBIAN-CVE-2026-93076","GHSA-m5cm-762c-jpjj","UBUNTU-CVE-2026-93076"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"A stale vmemmap_shift in the Linux kernel DAX subsystem can cause memory mapping errors when rebinding devices, potentially leading to system instability or crashes.","user_interaction":"not_required","vuln_class":"other"},"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 vmemmap_shift when binding static pgmap\n\nClear pgmap-\u003evmemmap_shift for static DAX devices. When rebinding a static\ndevice from device_dax (which may set vmemmap_shift based on alignment) to\nfsdev_dax, the stale vmemmap_shift persists on the shared pgmap. Explicitly\nzero it before devm_memremap_pages() so the vmemmap is built for order-0\nfolios as fsdev requires.","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 vmemmap_shift when binding static pgmap","id":"CVE-2026-93076","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"cxl/features: Clamp Get Feature output size to the remaining buffer","id":"CVE-2026-93077"},"packages":[],"prev":{"headline":"dax/fsdev: clear pgmap ops and owner on unbind","id":"CVE-2026-93075"},"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 stale vmemmap_shift in the Linux kernel DAX subsystem can cause memory mapping errors when rebinding devices, potentially leading to system instability or crashes.","url":"https://insights.sbomify.com/CVE-2026-93076/"}