Skip to main content
VulnerabilityPublished

CVE-2026-99726: Linux kernel · drm/v3d: Widen cache_clean_lock over the whole L2TCACTL sequence

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99726· Medium

Not known to be exploited · fixed in ea7ed4ab14f9ae79bd798bb156025bc751c71a9b : update Linux kernel when convenient.

Data as of 20 Nov 2026, 07:34 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in ea7ed4ab14f9ae79bd798bb156025bc751c71a9b, 994ba6e5c87d6a3d471ea987fe8622168f092334, 7.1 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=6.18.36 <6.18.64
  • >=7.0.13 <7.1
Fixed in
  • ea7ed4ab14f9ae79bd798bb156025bc751c71a9b
  • 994ba6e5c87d6a3d471ea987fe8622168f092334
  • 7.1
  • 6.18.64
  • 1b48fe8b323103e278fbc5145231b763577e2487
LinuxLinuxAffected
  • =7.1
Fixed in–

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.

References

Community reviews

Loading reviews…