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-2026-98785drm/amd/display: check dc_state_create_copy() for NULL in dm_suspend

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: check dc_state_create_copy() for NULL in dm_suspend dc_state_create_copy() can return NULL on allocation failure. dm_suspend() only conditionally skips dm_gpureset_toggle_interrupts() and continues execution, returning success. dm_resume() then dereferences the NULL cached_dc_state in link_enc_cfg_copy() and the following dc_state->stream_count loop, crashing during GPU reset recovery. Return -ENOMEM immediately if the copy fails, so the caller aborts suspend instead of leaving a NULL cached state for resume. (cherry picked from commit 84b6d7932fdd2857795a257f9f258562a3cddcab)

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 12 days 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.19% · top 92% of all CVEs (18 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected d0b8b23b9c2ebec693a36fea518d8f13493ad655 – < ed65678bb23a5f5040932960851ac39bdeafb765
    • affected 83c7f509ef087041604e9572938f82e18b724c9d – < 0b24f9d4e6e8ab64da8f2ae85bd1790d0f6a596f
    • affected 4cc2a94d96caeb3c975acdae7351c2f997c32175 – < 29302964ef583f3a57efc3c990bc0a71337bd3a4
    • affected 8092aa3ab8f7b737a34b71f91492c676a843043a – < 686baa1f4ec43b33e39e3d4b4a4539a91d17e883
    • affected 8092aa3ab8f7b737a34b71f91492c676a843043a – < 197946faa1b7968046ba475ae2f266847c6f51ed
    • affected 8092aa3ab8f7b737a34b71f91492c676a843043a – < 7283b78ca07ce491984a63f6288f3f8de5bdcb22
    • affected 8092aa3ab8f7b737a34b71f91492c676a843043a – < 015e72cde567d2450e282c2790773463156b2d0a
    • affected ea000e4b4ee5363997715531cb3d024b4e5d561c
    • affected 1686675405d07f35eae7ff3d13a530034b899df2
    • affected 5.15.165 – < 5.15.224
    • affected 6.1.105 – < 6.1.191
    • affected 6.6.46 – < 6.6.160
    • affected 5.10.258 – < 5.11
    • affected 6.10.5 – < 6.11
  • Linux · Linux

    • affected 6.11
    • unaffected < 6.11
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.56 – ≤ 6.18.*
    • unaffected 7.2.10 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .