drm/v3d: Widen cache_clean_lock over the whole L2TCACTL sequence
Summary
| CVE | CVE-2026-99726 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-11-20 06:18:09 UTC |
| Updated | 2026-11-20 06:18:09 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
drm/v3d: Widen cache_clean_lock over the whole L2TCACTL sequence
v3d_clean_caches() and v3d_flush_l2t() both write the single L2TCACTL
register and poll its status bits. The mutex cache_clean_lock exists to
serialize them, but v3d_clean_caches() only took the lock around its final
FLM_CLEAN write.
These functions run concurrently: v3d_flush_l2t() is issued from the
BIN/RENDER/CSD invalidate path while v3d_clean_caches() runs from the
CACHE_CLEAN queue, and each queue's scheduler uses its own ordered
workqueue, so their run_job callbacks execute in parallel.
Because clean locked only its final write, a concurrent flush can write
L2TCACTL during clean's unlocked phase. Both use non read-modify-write
writes to the one register, so whichever lands last wins: clean's TMUWCF
write can land on the flush's in-flight L2TFLS invalidate, triggering the
GFXH-1897 hazard of writing L2TCACTL while a flush is pending.
Hold cache_clean_lock across the entire L2TCACTL access sequence so it
is fully mutually exclusive with v3d_flush_l2t(), which already takes the
lock around its own write. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 11e9bdf8824b9e4e3c06d532c2663edb797c06f0 ea7ed4ab14f9ae79bd798bb156025bc751c71a9b git |
Not specified |
| CNA |
Linux |
Linux |
affected abf888b03a9805a3bc37948a0df443553b1c0910 1b48fe8b323103e278fbc5145231b763577e2487 git |
Not specified |
| CNA |
Linux |
Linux |
affected abf888b03a9805a3bc37948a0df443553b1c0910 994ba6e5c87d6a3d471ea987fe8622168f092334 git |
Not specified |
| CNA |
Linux |
Linux |
affected bdc2a495659f78ca01e6d5f18fb74419aaa1db0c git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.18.36 6.18.64 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 7.0.13 7.1 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 7.1 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.64 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3.5 7.3.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.4-rc2 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/1b48fe8b323103e278fbc5145231b763577e2487 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/ea7ed4ab14f9ae79bd798bb156025bc751c71a9b |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/994ba6e5c87d6a3d471ea987fe8622168f092334 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.