# CVE-2025-0044: Information disclosure in AMD Radeon™ PRO W7000 Series Graphics Products

> A local attacker with low privileges can exploit an out-of-bounds read in AMD power management firmware to disclose information and cause denial of service.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **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:** No
- **Published:** 15 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-vjjp-rpjm-8fq9

## What is CVE-2025-0044?

CVE-2025-0044 is a medium-severity vulnerability in AMD Radeon™ PRO W7000 Series Graphics Products, published on 15 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An out-of-bounds read in power management firmware by a malicious local attacker with low privileges could potentially lead to a partial loss of confidentiality and availability.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2025-0044?


## How do I fix CVE-2025-0044?

No fix has been published for CVE-2025-0044 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-0044 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0044 and fix it if it is affected.

What it is: CVE-2025-0044 is a medium-severity vulnerability in AMD Radeon™ PRO W7000 Series Graphics Products, published on 15 May 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-2025-0044 in the wild and no public exploit code.

Affected product: AMD Radeon™ PRO W7000 Series Graphics Products. 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-2025-0044/ (Markdown: https://insights.sbomify.com/CVE-2025-0044/index.md)
```

## Sources

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

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