drm/gud: validate GUD_ROTATION_0 is present in supported rotations
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/gud: validate GUD_ROTATION_0 is present in supported rotations
The rotation argument to drm_plane_create_rotation_property() is set to DRM_MODE_ROTATE_0, and the device reported rotation bitmask is used as the supported_rotations argument. The driver never validates that GUD_ROTATION_0 is present, so a device that omits it from its GUD_PROPERTY_ROTATION triggers the WARN_ON(rotation & ~supported_rotations) in drm_plane_create_rotation_property()
Fix this by skipping the creation of rotation property if the device doesn't have the GUD_ROTATION_0 bit
From the CVE record · Linux
The Linux kernel GUD display driver does not check whether a device reports GUD_ROTATION_0 as a supported rotation. A device that omits this bit from its rotation property triggers a kernel warning when the driver creates the rotation property. The input does not specify whether an attacker can control the device or whether authentication or user interaction is required.
Engineers running Linux kernels with the GUD display driver should check their deployments; affected versions are not specified.