{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72094 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72094 is a vulnerability in Linux, published on 15 Aug 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-72094 and fix it if it is affected.\n\nWhat it is: CVE-2026-72094 is a vulnerability in Linux, published on 15 Aug 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-72094 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-72094/ (Markdown: https://insights.sbomify.com/CVE-2026-72094/index.md)","id":"CVE-2026-72094","markdown":"https://insights.sbomify.com/CVE-2026-72094/index.md","name":"CVE-2026-72094","record":{"aliases":["DEBIAN-CVE-2026-72094","GHSA-cpm6-254x-7j7p","UBUNTU-CVE-2026-72094"],"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's dma-fence 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\ndma-buf: dma-fence: Fix potential NULL pointer dereference\n\nThe commit mentioned in the fixes tag below introduced a mechanism\nthrough which fence producers can fully decouple from fence consumers.\nThis, desirable, mechanism is based on the fence's signaled-bit as the\n\"decoupling point\".\n\nA sophisticated interaction between RCU and atomic instructions attempts\nto ensure that fence consumers can still interact with fence producers\nthrough the dma_fence_ops (callback pointers into the producer).\n\nThis is the desired behavior: to check for decoupling, the signaled-bit\nis first checked. If it's not yet signaled, RCU ensures that the ops\npointer cannot yet be NULL.\n\nHereby, dma_fence_signal_timestamp_locked() first sets the signaled-bit,\nand then sets the ops pointer to NULL. Readers first load the ops\npointer, and then check through the signaled-bit whether the pointer can\nlegally be accessed.\n\nThese set and load operations could occur out of order on weakly ordered\nplatforms. This problem can be solved very elegantly by using the ops\npointer itself as the synchronization point. The pointer is either NULL,\nor cannot become NULL while it is being used thanks to RCU.\n\nReplace the signaled-bit check in dma_fence_timeline_name() and\ndma_fence_driver_name().","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":"dma-buf: dma-fence: Fix potential NULL pointer dereference","id":"CVE-2026-72094","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"dma-fence: Make dma_fence_dedup_array() robust against 0-count input","id":"CVE-2026-72095"},"packages":[],"prev":{"headline":"accel/amdxdna: Fix use-after-free in amdxdna_gem_dmabuf_mmap()","id":"CVE-2026-72093"},"products":["Linux"],"published":"2026-08-15","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-08-17","vendors":["Linux"]},"summary":"A race condition in the Linux kernel's dma-fence subsystem can cause a NULL pointer dereference, leading to a system crash.","url":"https://insights.sbomify.com/CVE-2026-72094/"}