Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-50201drm/radeon: Fix encoder->possible_clones

Description

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)

Timeline

  1. ID reserved

    By Linux

  2. · 18 days later

    Published

  3. · 18 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-50201, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 74d2aacbe84042d89f572a3112a146fca05bfcb1 – < df75c78bfeff99f9b4815c3e79e2b1b1e34fe264
    • affected 74d2aacbe84042d89f572a3112a146fca05bfcb1 – < fda5dc80121b12871dc343ab37e0c3f0d138825d
    • affected 74d2aacbe84042d89f572a3112a146fca05bfcb1 – < c3cd27d85f0778f4ec07384d7516b33153759b8e
    • affected 74d2aacbe84042d89f572a3112a146fca05bfcb1 – < 1a235af0216411a32ab4db54f7bd19020b46c86d
    • affected 74d2aacbe84042d89f572a3112a146fca05bfcb1 – < 68801730ebb9393460b30cd3885e407f15da27a9
    • affected 74d2aacbe84042d89f572a3112a146fca05bfcb1 – < 28127dba64d8ae1a0b737b973d6d029908599611
  • Linux · Linux

    • affected 5.8
    • unaffected < 5.8
    • unaffected 5.10.228 – ≤ 5.10.*
    • unaffected 5.15.169 – ≤ 5.15.*
    • unaffected 6.1.114 – ≤ 6.1.*
    • unaffected 6.6.58 – ≤ 6.6.*
    • unaffected 6.11.5 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-50201 badge
[![CVE-2024-50201](https://cveledger.app/badge/CVE-2024-50201.svg)](https://cveledger.app/cve/CVE-2024-50201)

Record last updated .