# CVE-2025-31936: Privilege escalation in Intel(R) Xeon(R) 6 processors when using Intel(R) TDX

> A local adversary with privileged access can escalate privileges on Intel Xeon 6 processors using TDX due to improper memory overlap handling.

- **Severity:** High 7.0 (`CVSS:4.0/AV:L/AC:H/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:** 11 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** DEBIAN-CVE-2025-31936, GHSA-v7w9-9v5r-766h, UBUNTU-CVE-2025-31936

## What is CVE-2025-31936?

CVE-2025-31936 is a high-severity vulnerability in Intel(R) Xeon(R) 6 processors when using Intel(R) TDX, published on 11 Aug 2026. 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 processors when using Intel(R) TDX within SMM may allow an escalation of privilege. SMM adversary with a privileged user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are present with special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

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

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

It affects 73 products.


Products: Intel Xeon 6315p Firmware, Intel Xeon 6325p Firmware, Intel Xeon 6333p Firmware, Intel Xeon 6337p Firmware, Intel Xeon 6349p Firmware, Intel Xeon 6353p Firmware, Intel Xeon 6357p Firmware, Intel Xeon 6369p Firmware, Intel Xeon 6377p Firmware, Intel Xeon 6503p-B Firmware, Intel Xeon 6503p Firmware, Intel Xeon 6505p Firmware, Intel Xeon 6507p Firmware, Intel Xeon 6511p Firmware, Intel Xeon 6513p-B Firmware, Intel Xeon 6515p Firmware, Intel Xeon 6516p-B Firmware, Intel Xeon 6517p Firmware, Intel Xeon 6518p-B Firmware, Intel Xeon 6520p Firmware and 53 more.

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

Apply the vendor's patch.

## Is CVE-2025-31936 being exploited?

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

## Other vulnerabilities in Intel(R) Xeon(R) 6 processors when using Intel(R) TDX

- [CVE-2026-20898](https://insights.sbomify.com/CVE-2026-20898/): Privilege escalation in in Alias Checking Trusted Module for some Intel(R) Xeon(R) processors may allow an escalation of privilege. Startup code and SMM adversary with a privileged user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (high), integrity (high) and availability (none) impacts. (high 8.5)
- [CVE-2026-20716](https://insights.sbomify.com/CVE-2026-20716/): Privilege escalation in Intel(R) Processors (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-31936 is a high-severity vulnerability in Intel(R) Xeon(R) 6 processors when using Intel(R) TDX, published on 11 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-2025-31936 in the wild and no public exploit code.

Affected product: Intel(R) Xeon(R) 6 processors when using 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-31936/ (Markdown: https://insights.sbomify.com/CVE-2025-31936/index.md)
```

## Sources

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

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