CVE-2026-99726

Source
https://cve.org/CVERecord?id=CVE-2026-99726
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99726.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-99726
Published
2026-11-20T05:51:02Z
Modified
2026-11-20T07:01:13Z
Summary
drm/v3d: Widen cache_clean_lock over the whole L2TCACTL sequence
Details

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.

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99726.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
11e9bdf8824b9e4e3c06d532c2663edb797c06f0
Fixed
ea7ed4ab14f9ae79bd798bb156025bc751c71a9b
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
abf888b03a9805a3bc37948a0df443553b1c0910
Fixed
1b48fe8b323103e278fbc5145231b763577e2487
Fixed
994ba6e5c87d6a3d471ea987fe8622168f092334
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
bdc2a495659f78ca01e6d5f18fb74419aaa1db0c

Affected versions

v6.*
v6.18.36
v6.18.37
v6.18.38
v6.18.39
v6.18.40
v6.18.41
v6.18.42
v6.18.43
v6.18.44
v6.18.45
v6.18.46
v6.18.47
v6.18.48
v6.18.49
v6.18.50
v6.18.51
v6.18.52
v6.18.53
v6.18.54
v6.18.55
v6.18.56
v6.18.57
v6.18.58
v6.18.59
v6.18.60
v6.18.61
v6.18.62
v6.18.63
v7.*
v7.0.13
v7.0.14

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99726.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
6.18.36
Fixed
6.18.64
Type
ECOSYSTEM
Events
Introduced
7.0.13
Fixed
7.1
Type
ECOSYSTEM
Events
Introduced
7.1.0
Fixed
7.3.5

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99726.json"