{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93074 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93074 is a high-severity 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-93074 and fix it if it is affected.\n\nWhat it is: CVE-2026-93074 is a high-severity 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-93074 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-93074/ (Markdown: https://insights.sbomify.com/CVE-2026-93074/index.md)","id":"CVE-2026-93074","markdown":"https://insights.sbomify.com/CVE-2026-93074/index.md","name":"CVE-2026-93074","record":{"aliases":["DEBIAN-CVE-2026-93074","GHSA-hvvg-v8hj-gpv8","UBUNTU-CVE-2026-93074"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel DAX","requires_auth":"low_privilege","summary":"Incorrect kernel virtual address calculation in DAX direct access for multi-range devices could lead to memory access errors.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndax/fsdev: use __va(phys) for kaddr in direct_access\n\nUse __va(phys) instead of virt_addr + linear_offset for the kaddr\nreturn in __fsdev_dax_direct_access(). The previous code added a\ndevice-linear byte offset to virt_addr (which is __va of ranges[0]),\nbut for multi-range devices with physical gaps between ranges, this\nlinear arithmetic crosses the gap and produces a wrong kernel virtual\naddress. Using __va(phys) where phys comes from dax_pgoff_to_phys()\nis correct for any range layout because the direct map translates\neach physical address independently.\n\nThis leaves dev_dax-\u003evirt_addr write-only, so remove the field\n(suggested by Dave Jiang).","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: use __va(phys) for kaddr in direct_access","id":"CVE-2026-93074","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"dax/fsdev: clear pgmap ops and owner on unbind","id":"CVE-2026-93075"},"packages":[],"prev":{"headline":"dax: read holder_ops once in dax_holder_notify_failure()","id":"CVE-2026-93073"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"Incorrect kernel virtual address calculation in DAX direct access for multi-range devices could lead to memory access errors.","url":"https://insights.sbomify.com/CVE-2026-93074/"}