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-2025-39705drm/amd/display: fix a Null pointer dereference vulnerability

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: fix a Null pointer dereference vulnerability [Why] A null pointer dereference vulnerability exists in the AMD display driver's (DC module) cleanup function dc_destruct(). When display control context (dc->ctx) construction fails (due to memory allocation failure), this pointer remains NULL. During subsequent error handling when dc_destruct() is called, there's no NULL check before dereferencing the perf_trace member (dc->ctx->perf_trace), causing a kernel null pointer dereference crash. [How] Check if dc->ctx is non-NULL before dereferencing. (Updated commit text and removed unnecessary error message) (cherry picked from commit 9dd8e2ba268c636c240a918e0a31e6feaee19404)

Timeline

  1. ID reserved

    By Linux

  2. · 5 months later

    Published

  3. · 14 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-2025-39705, 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.20% · top 90% of all CVEs (12 Nov 2026)
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 – < dd9699368f37aca4f216857847a46a8a2c289f94
    • affected 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – < 0d9f4f202de1522aadc7a827aba0ae92b3d70937
    • affected 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – < 0961673cc5f0055957aa46f25eb4ef6c07e00165
    • affected 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – < 4ade995b9b25b3c6e8dc42c27070340f1358d8c8
    • affected 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – < 1bcf63a44381691d6192872801f830ce3250e367
  • Linux · Linux

    • affected 4.15
    • unaffected < 4.15
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.44 – ≤ 6.12.*
    • unaffected 6.16.4 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .