PT-2026-152606
CVE-2026-99726
·
Published
2026-11-20
·
Updated
2026-11-20
Description by
Score
N/A
Not availableNo severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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.
Found an issue in the description? Have something to add? Feel free to write us 👾