{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93073 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93073 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-93073 and fix it if it is affected.\n\nWhat it is: CVE-2026-93073 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-93073 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-93073/ (Markdown: https://insights.sbomify.com/CVE-2026-93073/index.md)","id":"CVE-2026-93073","markdown":"https://insights.sbomify.com/CVE-2026-93073/index.md","name":"CVE-2026-93073","record":{"aliases":["AZL-102710","BELL-CVE-2026-93073","DEBIAN-CVE-2026-93073","GHSA-xxf3-2jmr-5rfc","UBUNTU-CVE-2026-93073"],"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":"none","summary":"A race condition in the Linux kernel DAX subsystem can cause a null pointer dereference, leading to a system crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"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: read holder_ops once in dax_holder_notify_failure()\n\ndax_holder_notify_failure() reads dax_dev-\u003eholder_ops twice without\nREAD_ONCE() -- once for the NULL check and once for the indirect\nnotify_failure() call. A concurrent fs_put_dax() can clear holder_ops\nbetween the two reads, so the check can observe a non-NULL pointer while\nthe call dereferences NULL. (kill_dax() also clears holder_ops, but only\nafter synchronize_srcu(), so it cannot race a reader that is inside\ndax_read_lock(); fs_put_dax() does no such synchronization.)\n\nFetch holder_ops once into a local with READ_ONCE() so the NULL check and\nthe indirect call observe the same value.","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: read holder_ops once in dax_holder_notify_failure()","id":"CVE-2026-93073","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"dax/fsdev: use __va(phys) for kaddr in direct_access","id":"CVE-2026-93074"},"packages":[],"prev":{"headline":"irqchip/renesas-irqc: Fix generic interrupt chip leak on remove","id":"CVE-2026-93072"},"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 race condition in the Linux kernel DAX subsystem can cause a null pointer dereference, leading to a system crash.","url":"https://insights.sbomify.com/CVE-2026-93073/"}