CVE-2026-68445
drm/vc4: Prevent shader BO mappings from becoming writable
Description
In the Linux kernel, the following vulnerability has been resolved: drm/vc4: Prevent shader BO mappings from becoming writable vc4_gem_object_mmap() rejects a writable mapping of a validated shader BO, but leaves VM_MAYWRITE set. Userspace can map the BO read-only and then turn it writable with mprotect(). Validated shader BOs must stay read-only: the validator checks the instructions once and the GPU trusts them afterwards. A writable mapping lets userspace rewrite the code after validation, bypassing the validator. Clear VM_MAYWRITE on the read-only path so the mapping cannot be upgraded, as i915 already does for its read-only objects.
INFO
Published Date :
Aug. 12, 2026, 12:17 a.m.
Last Modified :
Aug. 12, 2026, 12:17 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-68445
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Clear VM_MAYWRITE on the read-only mapping path.
- Prevent userspace from upgrading read-only mappings to writable.
- Apply the fix to the Linux kernel's DRM/vc4 module.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-68445.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-68445 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-68445
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-68445 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-68445 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 12, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '463873d5701427f2964a0b4b72c45f1f14b6df87', 'lessThan': '9f0ee411fc2d76333d6087c5862ffa907cf7a175', 'versionType': 'git'}, {'status': 'affected', 'version': '463873d5701427f2964a0b4b72c45f1f14b6df87', 'lessThan': '019e6ad247f7fd038d2e009789f6d9bfcccb1ae7', 'versionType': 'git'}, {'status': 'affected', 'version': '463873d5701427f2964a0b4b72c45f1f14b6df87', 'lessThan': '6deaa317201851c644c431b57682e54d06b35838', 'versionType': 'git'}, {'status': 'affected', 'version': '463873d5701427f2964a0b4b72c45f1f14b6df87', 'lessThan': 'fe168ef1d232d734d9998fd74822e2e20930dfff', 'versionType': 'git'}, {'status': 'affected', 'version': '463873d5701427f2964a0b4b72c45f1f14b6df87', 'lessThan': '0c9e6367639548307d3f578f6943ce72c9d39087', 'versionType': 'git'}], 'programFiles': ['drivers/gpu/drm/vc4/vc4_bo.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '4.5'}, {'status': 'unaffected', 'version': '0', 'lessThan': '4.5', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.6.148', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.101', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.42', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.6', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc5', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/gpu/drm/vc4/vc4_bo.c'], 'defaultStatus': 'affected'}] Added Description In the Linux kernel, the following vulnerability has been resolved: drm/vc4: Prevent shader BO mappings from becoming writable vc4_gem_object_mmap() rejects a writable mapping of a validated shader BO, but leaves VM_MAYWRITE set. Userspace can map the BO read-only and then turn it writable with mprotect(). Validated shader BOs must stay read-only: the validator checks the instructions once and the GPU trusts them afterwards. A writable mapping lets userspace rewrite the code after validation, bypassing the validator. Clear VM_MAYWRITE on the read-only path so the mapping cannot be upgraded, as i915 already does for its read-only objects. Added Reference https://git.kernel.org/stable/c/019e6ad247f7fd038d2e009789f6d9bfcccb1ae7 Added Reference https://git.kernel.org/stable/c/0c9e6367639548307d3f578f6943ce72c9d39087 Added Reference https://git.kernel.org/stable/c/6deaa317201851c644c431b57682e54d06b35838 Added Reference https://git.kernel.org/stable/c/9f0ee411fc2d76333d6087c5862ffa907cf7a175 Added Reference https://git.kernel.org/stable/c/fe168ef1d232d734d9998fd74822e2e20930dfff