# CVE-2021-26333: AMD Chipset Driver Information Disclosure Vulnerability

> Low-privileged users can leak data from uninitialized physical pages via the AMD PSP driver due to improper access control.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A: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:** 21 Sep 2021
- **Updated:** 28 May 2026
- **Also known as:** GHSA-rw97-q7v4-xhhq

## What is CVE-2021-26333?

CVE-2021-26333 is a medium-severity vulnerability in AMD PSP Driver, published on 21 Sep 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An information disclosure vulnerability exists in AMD Platform Security Processor (PSP) chipset driver. The discretionary access control list (DACL) may allow low privileged users to open a handle and send requests to the driver resulting in a potential data leak from uninitialized physical pages.

Weakness: CWE-909 (Missing Initialization of Resource), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2021-26333?

It affects 2 products.


Products: Amd Chipset Driver, Amd Psp Driver.

## How do I fix CVE-2021-26333?

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

## Is CVE-2021-26333 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-26333 and fix it if it is affected.

What it is: CVE-2021-26333 is a medium-severity vulnerability in AMD PSP Driver, published on 21 Sep 2021. 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-2021-26333 in the wild and no public exploit code.

Affected product: AMD PSP Driver. 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-2021-26333/ (Markdown: https://insights.sbomify.com/CVE-2021-26333/index.md)
```

## Sources

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

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