# CVE-2026-93175: drm/amd/display: Fix dangling pointer in CRTC reset function

> A dangling pointer in the AMD display driver allows attackers to trigger use-after-free conditions, potentially leading to code execution or system crashes.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-102309, BELL-CVE-2026-93175, DEBIAN-CVE-2026-93175, GHSA-7g8p-mffc-5643, UBUNTU-CVE-2026-93175

## What is CVE-2026-93175?

CVE-2026-93175 is a high-severity use after free vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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]

## Which versions are affected by CVE-2026-93175?


## How do I fix CVE-2026-93175?

Apply the vendor's patch.

## Is CVE-2026-93175 being exploited?

There is no known exploitation of CVE-2026-93175 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93175 and fix it if it is affected.

What it is: CVE-2026-93175 is a high-severity use after free vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93175 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93175/ (Markdown: https://insights.sbomify.com/CVE-2026-93175/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93175
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93175
- OSV: https://osv.dev/vulnerability/CVE-2026-93175

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93175/
Summaries are generated and may contain mistakes; the official description above is the record.