{"api_version":"1","generated_at":"2026-11-20T07:30:02+00:00","cve":"CVE-2026-99726","urls":{"html":"https://cve.report/CVE-2026-99726","api":"https://cve.report/api/cve/CVE-2026-99726.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99726","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99726"},"summary":{"title":"drm/v3d: Widen cache_clean_lock over the whole L2TCACTL sequence","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/v3d: Widen cache_clean_lock over the whole L2TCACTL sequence\n\nv3d_clean_caches() and v3d_flush_l2t() both write the single L2TCACTL\nregister and poll its status bits. The mutex cache_clean_lock exists to\nserialize them, but v3d_clean_caches() only took the lock around its final\nFLM_CLEAN write.\n\nThese functions run concurrently: v3d_flush_l2t() is issued from the\nBIN/RENDER/CSD invalidate path while v3d_clean_caches() runs from the\nCACHE_CLEAN queue, and each queue's scheduler uses its own ordered\nworkqueue, so their run_job callbacks execute in parallel.\n\nBecause clean locked only its final write, a concurrent flush can write\nL2TCACTL during clean's unlocked phase. Both use non read-modify-write\nwrites to the one register, so whichever lands last wins: clean's TMUWCF\nwrite can land on the flush's in-flight L2TFLS invalidate, triggering the\nGFXH-1897 hazard of writing L2TCACTL while a flush is pending.\n\nHold cache_clean_lock across the entire L2TCACTL access sequence so it\nis fully mutually exclusive with v3d_flush_l2t(), which already takes the\nlock around its own write.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-11-20 06:18:09","updated_at":"2026-11-20 06:18:09"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/1b48fe8b323103e278fbc5145231b763577e2487","name":"https://git.kernel.org/stable/c/1b48fe8b323103e278fbc5145231b763577e2487","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/ea7ed4ab14f9ae79bd798bb156025bc751c71a9b","name":"https://git.kernel.org/stable/c/ea7ed4ab14f9ae79bd798bb156025bc751c71a9b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/994ba6e5c87d6a3d471ea987fe8622168f092334","name":"https://git.kernel.org/stable/c/994ba6e5c87d6a3d471ea987fe8622168f092334","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99726","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99726","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 11e9bdf8824b9e4e3c06d532c2663edb797c06f0 ea7ed4ab14f9ae79bd798bb156025bc751c71a9b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected abf888b03a9805a3bc37948a0df443553b1c0910 1b48fe8b323103e278fbc5145231b763577e2487 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected abf888b03a9805a3bc37948a0df443553b1c0910 994ba6e5c87d6a3d471ea987fe8622168f092334 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected bdc2a495659f78ca01e6d5f18fb74419aaa1db0c git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.18.36 6.18.64 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.0.13 7.1 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.1","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.64 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3.5 7.3.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.4-rc2 * 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_gem.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"ea7ed4ab14f9ae79bd798bb156025bc751c71a9b","status":"affected","version":"11e9bdf8824b9e4e3c06d532c2663edb797c06f0","versionType":"git"},{"lessThan":"1b48fe8b323103e278fbc5145231b763577e2487","status":"affected","version":"abf888b03a9805a3bc37948a0df443553b1c0910","versionType":"git"},{"lessThan":"994ba6e5c87d6a3d471ea987fe8622168f092334","status":"affected","version":"abf888b03a9805a3bc37948a0df443553b1c0910","versionType":"git"},{"status":"affected","version":"bdc2a495659f78ca01e6d5f18fb74419aaa1db0c","versionType":"git"},{"lessThan":"6.18.64","status":"affected","version":"6.18.36","versionType":"semver"},{"lessThan":"7.1","status":"affected","version":"7.0.13","versionType":"semver"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/gpu/drm/v3d/v3d_gem.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"7.1"},{"lessThan":"7.1","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.64","versionType":"semver"},{"lessThanOrEqual":"7.3.*","status":"unaffected","version":"7.3.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.4-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.64","versionStartIncluding":"6.18.36","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3.5","versionStartIncluding":"7.1","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.4-rc2","versionStartIncluding":"7.1","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"7.0.13","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/v3d: Widen cache_clean_lock over the whole L2TCACTL sequence\n\nv3d_clean_caches() and v3d_flush_l2t() both write the single L2TCACTL\nregister and poll its status bits. The mutex cache_clean_lock exists to\nserialize them, but v3d_clean_caches() only took the lock around its final\nFLM_CLEAN write.\n\nThese functions run concurrently: v3d_flush_l2t() is issued from the\nBIN/RENDER/CSD invalidate path while v3d_clean_caches() runs from the\nCACHE_CLEAN queue, and each queue's scheduler uses its own ordered\nworkqueue, so their run_job callbacks execute in parallel.\n\nBecause clean locked only its final write, a concurrent flush can write\nL2TCACTL during clean's unlocked phase. Both use non read-modify-write\nwrites to the one register, so whichever lands last wins: clean's TMUWCF\nwrite can land on the flush's in-flight L2TFLS invalidate, triggering the\nGFXH-1897 hazard of writing L2TCACTL while a flush is pending.\n\nHold cache_clean_lock across the entire L2TCACTL access sequence so it\nis fully mutually exclusive with v3d_flush_l2t(), which already takes the\nlock around its own write."}],"providerMetadata":{"dateUpdated":"2026-11-20T05:51:02.156Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/ea7ed4ab14f9ae79bd798bb156025bc751c71a9b"},{"url":"https://git.kernel.org/stable/c/1b48fe8b323103e278fbc5145231b763577e2487"},{"url":"https://git.kernel.org/stable/c/994ba6e5c87d6a3d471ea987fe8622168f092334"}],"title":"drm/v3d: Widen cache_clean_lock over the whole L2TCACTL sequence","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99726","datePublished":"2026-11-20T05:51:02.156Z","dateReserved":"2026-09-25T10:25:14.431Z","dateUpdated":"2026-11-20T05:51:02.156Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 06:18:09","lastModifiedDate":"2026-11-20 06:18:09","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99726","Ordinal":"1","Title":"drm/v3d: Widen cache_clean_lock over the whole L2TCACTL sequence","CVE":"CVE-2026-99726","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99726","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/v3d: Widen cache_clean_lock over the whole L2TCACTL sequence\n\nv3d_clean_caches() and v3d_flush_l2t() both write the single L2TCACTL\nregister and poll its status bits. The mutex cache_clean_lock exists to\nserialize them, but v3d_clean_caches() only took the lock around its final\nFLM_CLEAN write.\n\nThese functions run concurrently: v3d_flush_l2t() is issued from the\nBIN/RENDER/CSD invalidate path while v3d_clean_caches() runs from the\nCACHE_CLEAN queue, and each queue's scheduler uses its own ordered\nworkqueue, so their run_job callbacks execute in parallel.\n\nBecause clean locked only its final write, a concurrent flush can write\nL2TCACTL during clean's unlocked phase. Both use non read-modify-write\nwrites to the one register, so whichever lands last wins: clean's TMUWCF\nwrite can land on the flush's in-flight L2TFLS invalidate, triggering the\nGFXH-1897 hazard of writing L2TCACTL while a flush is pending.\n\nHold cache_clean_lock across the entire L2TCACTL access sequence so it\nis fully mutually exclusive with v3d_flush_l2t(), which already takes the\nlock around its own write.","Type":"Description","Title":"drm/v3d: Widen cache_clean_lock over the whole L2TCACTL sequence"}]}}}