Bug 2514448 (CVE-2026-68445) - CVE-2026-68445 kernel: drm/vc4: Prevent shader BO mappings from becoming writable
Summary: CVE-2026-68445 kernel: drm/vc4: Prevent shader BO mappings from becoming writ...
Keywords:
Status: NEW
Alias: CVE-2026-68445
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-12 00:21 UTC by OSIDB Bzimport
Modified: 2026-08-13 09:12 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-12 00:21:59 UTC
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.

Comment 1 Mauro Matteo Cascella 2026-08-12 15:19:06 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026081257-CVE-2026-68445-00a0@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.