Skip to main content
VulnerabilityPublished

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

Affects Linux kernelSource CVE Database V5

0
Compare

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

Data as of 20 Nov 2026, 06:34 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · 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–

AI-suggested

A fix is available and has been applied in Linux kernel versions 6.18.64 and 7.1, as well as specific commits identified by their hashes. Users and administrators should update to these fixed versions to mitigate the vulnerability. No additional mitigation actions are required beyond applying the official fix.

Description

A concurrency issue in the Linux kernel's drm/v3d driver was fixed by widening the cache_clean_lock to cover the entire L2TCACTL register access sequence. Previously, concurrent writes to the L2TCACTL register by v3d_clean_caches() and v3d_flush_l2t() could cause a race condition leading to a hardware hazard. This was resolved by ensuring mutual exclusion during the entire register access to prevent conflicting writes.

References

Community reviews

Loading reviews…