{"uuid": "246fb3a6-ac19-423b-a929-f7c4e6e4c77b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-50201", "type": "seen", "source": "https://t.me/cvedetector/10170", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50201 - Radeon DRM Possible Clones Validation Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50201 \nPublished : Nov. 8, 2024, 6:15 a.m. | 41\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/radeon: Fix encoder->possible_clones  \n  \nInclude the encoder itself in its possible_clones bitmask.  \nIn the past nothing validated that drivers were populating  \npossible_clones correctly, but that changed in commit  \n74d2aacbe840 (\"drm: Validate encoder->possible_clones\").  \nLooks like radeon never got the memo and is still not  \nfollowing the rules 100% correctly.  \n  \nThis results in some warnings during driver initialization:  \nBogus possible_clones: [ENCODER:46:TV-46] possible_clones=0x4 (full encoder mask=0x7)  \nWARNING: CPU: 0 PID: 170 at drivers/gpu/drm/drm_mode_config.c:615 drm_mode_config_validate+0x113/0x39c  \n...  \n  \n(cherry picked from commit 3b6e7d40649c0d75572039aff9d0911864c689db) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-08T07:59:43.000000Z"}