# CVE-2026-74450: drm/amd/pm: fix pptable use-after-free

> A use-after-free in the Linux kernel AMD power management driver allows local attackers to potentially execute code or escalate privileges via concurrent sysfs access.

- **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:** 15 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** AZL-96249, BELL-CVE-2026-74450, DEBIAN-CVE-2026-74450, GHSA-w7rg-pqcq-fh8p, UBUNTU-CVE-2026-74450

## What is CVE-2026-74450?

CVE-2026-74450 is a high-severity use after free vulnerability in Linux, published on 15 Aug 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/pm: fix pptable use-after-free

amdgpu_dpm_get_pp_table() returns a pointer to a driver-owned power table
after dropping adev->pm.mutex. The sysfs path then copies from that pointer.
A concurrent pp_table write can replace and free the allocation during the
copy, causing a use-after-free.

Change the DPM interface to copy into caller-provided storage while the mutex
is held. Keep the size-only query for attribute discovery without exposing
the driver-owned pointer.

(cherry picked from commit f6eed7acfd30099ef7baeb6ba45bb59daad80631)

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


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

Apply the vendor's patch.

## Is CVE-2026-74450 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74450 is a high-severity use after free vulnerability in Linux, published on 15 Aug 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-74450 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-74450/ (Markdown: https://insights.sbomify.com/CVE-2026-74450/index.md)
```

## Sources

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

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