drm/amd/display: Fix dangling pointer in CRTC reset function
CVE-2026-93175 · published 17 Sept 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-93175?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: e7b07ceef2a650e5ed8ca37997689e086c680daf to < ef3293c87a79f734d506769ff86f99bf1bad522e, e7b07ceef2a650e5ed8ca37997689e086c680daf to < 9de069b724f3614ed7dd55bfbb37c434db54e128, e7b07ceef2a650e5ed8ca37997689e086c680daf to < 3a03827bb3cda1527aa923f18160c449f2b4cf2c, e7b07ceef2a650e5ed8ca37997689e086c680daf to < 32bd68edbc6cbcfac0e4033b64f0bcadbf0efef5
- Linux Linux: 4.15
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Fix dangling pointer in CRTC reset function
amdgpu_dm_crtc_reset_state() frees the old state before allocating
a new one. If kzalloc() fails, the function returns without updating
the state pointer, leaving a dangling pointer to already freed memory.
Fix this by allocating the new state first. On allocation failure, the
old state remains untouched and the function safely returns.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
[adjust for movement around current amd-staging-drm-next]
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/ef3293c87a79f734d506769ff86f99bf1bad522e
- git.kernel.org/stable/c/9de069b724f3614ed7dd55bfbb37c434db54e128
- git.kernel.org/stable/c/3a03827bb3cda1527aa923f18160c449f2b4cf2c
- git.kernel.org/stable/c/32bd68edbc6cbcfac0e4033b64f0bcadbf0efef5
- git.kernel.org/stable/c/0aeed866cb938943908c3ba46422128e49d2d080
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON