drm/radeon: Fix encoder->possible_clones
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 74d2aacbe84042d89f572a3112a146fca05bfcb1 · < 28127dba64d8ae1a0b737b973d6d029908599611| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/radeon: Fix encoder->possible_clones
Include the encoder itself in its possible_clones bitmask. In the past nothing validated that drivers were populating possible_clones correctly, but that changed in commit 74d2aacbe840 ("drm: Validate encoder->possible_clones"). Looks like radeon never got the memo and is still not following the rules 100% correctly.
This results in some warnings during driver initialization: Bogus possible_clones: [ENCODER:46:TV-46] possible_clones=0x4 (full encoder mask=0x7) WARNING: CPU: 0 PID: 170 at drivers/gpu/drm/drm_mode_config.c:615 drm_mode_config_validate+0x113/0x39c ...
(cherry picked from commit 3b6e7d40649c0d75572039aff9d0911864c689db)
From the CVE record · Linux
The Linux kernel’s radeon driver does not include an encoder itself in its possible_clones bitmask, as required by DRM validation. This can trigger warnings during driver initialization. The input does not describe an attacker action or specify network access, authentication, or user interaction requirements.
Engineers running Linux kernels with the radeon driver should check their installations; affected versions are not specified.