{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93047 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93047 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-93047 and fix it if it is affected.\n\nWhat it is: CVE-2026-93047 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-93047 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-93047/ (Markdown: https://insights.sbomify.com/CVE-2026-93047/index.md)","id":"CVE-2026-93047","markdown":"https://insights.sbomify.com/CVE-2026-93047/index.md","name":"CVE-2026-93047","record":{"aliases":["AZL-102056","BELL-CVE-2026-93047","DEBIAN-CVE-2026-93047","GHSA-75w8-rpch-q4h9","UBUNTU-CVE-2026-93047"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel v3d driver allows local attackers to cause data corruption by reading buffer objects while another context writes them.","user_interaction":"not_required","vuln_class":"race_condition"},"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\ndrm/v3d: Associate BOs with every job that accesses them\n\nA submission can expand into a chain of jobs (e.g. bin + render + cache\nclean). Implicit synchronization in v3d_submit_lock_reservations() is gated\non each job's bo[], but the BO list was only ever attached to the last job\nof the chain. When that last job is a trailing CACHE_CLEAN job, the job\nthat actually consumes the BOs (that is, a RENDER or CSD job) was left with\nbo_count == 0 and picked up no implicit dependencies. It could therefore\nbe dispatched to the hardware and read a BO while another context was still\nwriting it, leading to data corruption.\n\nAttach the BOs to the job that consumes them, so (1) it acquires the\ncorrect implicit dependencies during reservation locking and (2) they are\nkept mapped until the end of the submission. Give it references to all\nconsuming job's BOs through v3d_job_reference_bos() instead of looking the\nhandles up a second time; that avoids a redundant lookup and guarantees\nboth jobs reference the exact same objects.\n\nAs the CACHE_CLEAN job now carries a BO array as well, add a per-job\n`has_implicit_dep` flag so that only the consuming jobs take implicit\ndependencies. The CACHE_CLEAN job (a global flush) and the BIN job (binning\nwaiting on another context is not a realistic scenario) are excluded.","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":"drm/v3d: Associate BOs with every job that accesses them","id":"CVE-2026-93047","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"mtd: part: reject MTDPART_OFS_RETAIN in mtd_add_partition()","id":"CVE-2026-93048"},"packages":[],"prev":{"headline":"software node: Fix software_node_get_reference_args() with index -1","id":"CVE-2026-93046"},"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 v3d driver allows local attackers to cause data corruption by reading buffer objects while another context writes them.","url":"https://insights.sbomify.com/CVE-2026-93047/"}