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-50003

drm/amd/display: Fix system hang while resume with TBT monitor

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix system hang while resume with TBT monitor [Why] Connected with a Thunderbolt monitor and do the suspend and the system may hang while resume. The TBT monitor HPD will be triggered during the resume procedure and call the drm_client_modeset_probe() while struct drm_connector connector->dev->master is NULL. It will mess up the pipe topology after resume. [How] Skip the TBT monitor HPD during the resume procedure because we currently will probe the connectors after resume by default. (cherry picked from commit 453f86a26945207a16b8f66aaed5962dc2b95b85)

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 19 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-50003, by who scored it
Scored byCVSSScoreVector
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.22% · top 87% of all CVEs (11 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 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – < eb9329cd882aa274e92bdb1003bc088433fdee86
    • affected 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – < 722d2d8fc423108597b97efbf165187d16d9aa1e
    • affected 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – < 68d603f467a75618eeae5bfe8af32cda47097010
    • affected 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – < 73e441be033d3ed0bdff09b575da3e7d4606ffc9
    • affected 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – < c2356296f546326f9f06c109e201d42201e1e783
    • affected 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – < 52d4e3fb3d340447dcdac0e14ff21a764f326907
  • Linux · Linux

    • affected 4.15
    • unaffected < 4.15
    • unaffected 5.15.168 – ≤ 5.15.*
    • unaffected 6.1.113 – ≤ 6.1.*
    • unaffected 6.6.55 – ≤ 6.6.*
    • unaffected 6.10.14 – ≤ 6.10.*
    • unaffected 6.11.3 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .