# CVE-2025-22889: Privilege escalation in Intel(R) Xeon(R) 6 processor with Intel(R) TDX

> A privileged local attacker can escalate privileges due to improper handling of protected memory range overlaps in Intel Xeon 6 processors with TDX.

- **Severity:** High 7.0 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Aug 2025
- **Updated:** 26 Feb 2026
- **Also known as:** ALPINE-CVE-2025-22889, BELL-CVE-2025-22889, DEBIAN-CVE-2025-22889, GHSA-x9p4-6h68-vm5q, UBUNTU-CVE-2025-22889

## What is CVE-2025-22889?

CVE-2025-22889 is a high-severity vulnerability in Intel(R) Xeon(R) 6 processor with Intel(R) TDX, published on 12 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper handling of overlap between protected memory ranges for some Intel(R) Xeon(R) 6 processor with Intel(R) TDX may allow a privileged user to potentially enable escalation of privilege via local access.

Weakness: CWE-1260 (Improper Handling of Overlap Between Protected Memory Ranges)

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


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

Apply the vendor's patch.

## Is CVE-2025-22889 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-22889 is a high-severity vulnerability in Intel(R) Xeon(R) 6 processor with Intel(R) TDX, published on 12 Aug 2025. 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-22889 in the wild and no public exploit code.

Affected product: Intel(R) Xeon(R) 6 processor with Intel(R) TDX. 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-22889/ (Markdown: https://insights.sbomify.com/CVE-2025-22889/index.md)
```

## Sources

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

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