drm/vc4: Prevent shader BO mappings from becoming writable
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 463873d5701427f2964a0b4b72c45f1f14b6df87 · < 0c9e6367639548307d3f578f6943ce72c9d39087| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s drm/vc4 component leaves validated shader buffer mappings eligible for write access. Local userspace can map a buffer read-only, make it writable with mprotect(), and change shader code after validation, bypassing the validator.
Engineers running Linux kernels that use the drm/vc4 component should check their deployments; affected versions were not specified.