Driver initialization warnings via incomplete clone bitmask
Published Nov 8, 2024 · Updated May 11, 2026
Improper encoder clone-mask handling in Linux 5.8 through affected branches allows local users to trigger driver initialization warnings. In drivers/gpu/drm/radeon/radeon_encoders.c, Radeon encoder setup omits each encoder's own bit from possible_clones, so DRM validation reports a bogus mask and emits a kernel warning. Reachability requires a locally accessible system using the affected Radeon driver and encoder path; published evidence demonstrates initialization warnings but does not document a panic or data compromise.
Summary
What happened
Improper encoder clone-mask handling in Linux 5.8 through affected branches allows local users to trigger driver initialization warnings. In drivers/gpu/drm/radeon/radeon_encoders.c, Radeon encoder setup omits each encoder's own bit from possible_clones, so DRM validation reports a bogus mask and emits a kernel warning. Reachability requires a locally accessible system using the affected Radeon driver and encoder path; published evidence demonstrates initialization warnings but does not document a panic or data compromise.
The record
- CVE
- CVE-2024-50201
- Published
- Nov 8, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 8, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.8
- Affected versionversion=74d2aacbe84042d89f572a3112a146fca05bfcb1 <1a235af0216411a32ab4db54f7bd19020b46c86d
- Affected versionversion=74d2aacbe84042d89f572a3112a146fca05bfcb1 <28127dba64d8ae1a0b737b973d6d029908599611
- Affected versionversion=74d2aacbe84042d89f572a3112a146fca05bfcb1 <68801730ebb9393460b30cd3885e407f15da27a9
- Affected versionversion=74d2aacbe84042d89f572a3112a146fca05bfcb1 <c3cd27d85f0778f4ec07384d7516b33153759b8e
- Affected versionversion=74d2aacbe84042d89f572a3112a146fca05bfcb1 <df75c78bfeff99f9b4815c3e79e2b1b1e34fe264
- Affected versionversion=74d2aacbe84042d89f572a3112a146fca05bfcb1 <fda5dc80121b12871dc343ab37e0c3f0d138825d
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo