NetSight
unscored

CVE-2026-99726

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…

Impact

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.

Affected products · Linux

ProductAffected versions
Linux
from 11e9bdf8824b9e4e3c06d532c2663edb797c06f0 before ea7ed4ab14f9ae79bd798bb156025bc751c71a9b
from abf888b03a9805a3bc37948a0df443553b1c0910 before 1b48fe8b323103e278fbc5145231b763577e2487
from abf888b03a9805a3bc37948a0df443553b1c0910 before 994ba6e5c87d6a3d471ea987fe8622168f092334
from 6.18.36 before 6.18.64
from 7.0.13 before 7.1
Version bdc2a495659f78ca01e6d5f18fb74419aaa1db0c

References