{"api_version":"1","generated_at":"2026-09-17T22:01:40+00:00","cve":"CVE-2026-93047","urls":{"html":"https://cve.report/CVE-2026-93047","api":"https://cve.report/api/cve/CVE-2026-93047.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-93047","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-93047"},"summary":{"title":"drm/v3d: Associate BOs with every job that accesses them","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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-17 17:17:57","updated_at":"2026-09-17 17:17:57"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/fa98563ab00dbe62fcedfef6bdd34ded7a860d9f","name":"https://git.kernel.org/stable/c/fa98563ab00dbe62fcedfef6bdd34ded7a860d9f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/7244dd0f12629484a1936dc5c5837670d8d9f80c","name":"https://git.kernel.org/stable/c/7244dd0f12629484a1936dc5c5837670d8d9f80c","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-93047","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93047","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected dffa9b7a78c4361e55e21b3acb54e0d34ad15ea0 7244dd0f12629484a1936dc5c5837670d8d9f80c git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected dffa9b7a78c4361e55e21b3acb54e0d34ad15ea0 fa98563ab00dbe62fcedfef6bdd34ded7a860d9f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.3","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.3 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.6 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/gpu/drm/v3d/v3d_drv.h","drivers/gpu/drm/v3d/v3d_submit.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"7244dd0f12629484a1936dc5c5837670d8d9f80c","status":"affected","version":"dffa9b7a78c4361e55e21b3acb54e0d34ad15ea0","versionType":"git"},{"lessThan":"fa98563ab00dbe62fcedfef6bdd34ded7a860d9f","status":"affected","version":"dffa9b7a78c4361e55e21b3acb54e0d34ad15ea0","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/gpu/drm/v3d/v3d_drv.h","drivers/gpu/drm/v3d/v3d_submit.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.3"},{"lessThan":"5.3","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.6","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.6","versionStartIncluding":"5.3","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"5.3","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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."}],"providerMetadata":{"dateUpdated":"2026-09-17T16:10:38.350Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/7244dd0f12629484a1936dc5c5837670d8d9f80c"},{"url":"https://git.kernel.org/stable/c/fa98563ab00dbe62fcedfef6bdd34ded7a860d9f"}],"title":"drm/v3d: Associate BOs with every job that accesses them","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-93047","datePublished":"2026-09-17T16:10:38.350Z","dateReserved":"2026-09-17T15:57:05.658Z","dateUpdated":"2026-09-17T16:10:38.350Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-17 17:17:57","lastModifiedDate":"2026-09-17 17:17:57","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"93047","Ordinal":"1","Title":"drm/v3d: Associate BOs with every job that accesses them","CVE":"CVE-2026-93047","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"93047","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"drm/v3d: Associate BOs with every job that accesses them"}]}}}