Live › vulnerability › CVE-2026-98785
Go to dashboardThe AMD display driver in the Linux kernel did not check whether a copied display state allocation succeeded during suspend. On allocation failure, resume dereferences a NULL pointer and the GPU reset recovery crashes.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with the AMD display (amdgpu DC) driver that can hit a memory allocation failure during suspend. The sources do not say how often that failure occurs in practice. Systems without AMD GPUs can skip it.
No product ranges from the sources yet.
uname -r to see the running kernel versionlsmod | grep amdgpu to confirm the AMD GPU driver is loadedEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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)
This page as .md · .json · in your agent: get_signal("CVE-2026-98785")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.