CVE-2025-31936· NVD / CVE Program· CNA intel

Improper handling of overlap between protected memory ranges for some Intel(R) Xeon(R) 6 processors when using Intel(R) TDX within SMM may a

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.

HighCVSS 7.0 · v4.0—No exploit Fix available

Local privilege escalation

Published: Aug 11, 2026
Updated: Sep 29, 2026
EPSS: 0.1% · 1th percentile
CWE: CWE-1260

Follow this CVE

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 28 / 40 · 7.0 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · intel: 7.0; NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

Vendor	Product	CPE
intel	xeon 6337p firmware	cpe:2.3:o:intel:xeon_6337p_firmware
intel	xeon 6337p	cpe:2.3:h:intel:xeon_6337p
intel	xeon 6349p firmware	cpe:2.3:o:intel:xeon_6349p_firmware
intel	xeon 6349p	cpe:2.3:h:intel:xeon_6349p
intel	xeon 6353p firmware	cpe:2.3:o:intel:xeon_6353p_firmware
intel	xeon 6353p	cpe:2.3:h:intel:xeon_6353p
intel	xeon 6357p firmware	cpe:2.3:o:intel:xeon_6357p_firmware
intel	xeon 6357p	cpe:2.3:h:intel:xeon_6357p
intel	xeon 6369p firmware	cpe:2.3:o:intel:xeon_6369p_firmware
intel	xeon 6369p	cpe:2.3:h:intel:xeon_6369p
intel	xeon 6377p firmware	cpe:2.3:o:intel:xeon_6377p_firmware
intel	xeon 6377p	cpe:2.3:h:intel:xeon_6377p

and 134 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

intel xeon 6315p firmwareall versions
intel xeon 6325p firmwareall versions
intel xeon 6333p firmwareall versions
intel xeon 6337p firmwareall versions
intel xeon 6349p firmwareall versions
intel xeon 6353p firmwareall versions
intel xeon 6357p firmwareall versions
intel xeon 6369p firmwareall versions
intel xeon 6377p firmwareall versions
intel xeon 6503p firmwareall versions
intel xeon 6503p-b firmwareall versions
intel xeon 6505p firmwareall versions
intel xeon 6507p firmwareall versions
intel xeon 6511p firmwareall versions
intel xeon 6513p-b firmwareall versions
intel xeon 6515p firmwareall versions
intel xeon 6516p-b firmwareall versions
intel xeon 6517p firmwareall versions
intel xeon 6518p-b firmwareall versions
intel xeon 6520p firmwareall versions

Versions reported by the vendor

Affected version ranges reported by the assigning authority (intel). Independent of NVD's CPE analysis and usually ahead of it.

n/a Intel(R) Xeon(R) 6 processors when using Intel(R) TDX
- See referencesaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
AlmaLinux:10	microcode_ctl	before 4:20260812-0.el10_2	4:20260812-0.el10_2
AlmaLinux:8	microcode_ctl	before 4:20260812-1.el8_10	4:20260812-1.el8_10
AlmaLinux:9	microcode_ctl	before 4:20260210-1.20260812.1.el9_8	4:20260210-1.20260812.1.el9_8
Debian:12	intel-microcode	all versions	—
openSUSE:Leap 16.0	ucode-intel	before 20260812-160000.1.1	20260812-160000.1.1
openSUSE:Tumbleweed	ucode-intel	before 20260812-1.1	20260812-1.1
Red Hat:enterprise_linux:10.2	microcode_ctl	before 4:20260812-0.el10_2	4:20260812-0.el10_2
Red Hat:enterprise_linux:8::baseos	microcode_ctl	before 4:20260812-1.el8_10	4:20260812-1.el8_10
Red Hat:enterprise_linux:9::baseos	microcode_ctl	before 4:20260210-1.20260812.1.el9_8	4:20260210-1.20260812.1.el9_8
Rocky Linux:10	microcode_ctl	before 4:20260812-0.el10_2	4:20260812-0.el10_2
Rocky Linux:8	microcode_ctl	before 4:20260812-1.el8_10	4:20260812-1.el8_10
Rocky Linux:9	microcode_ctl	before 4:20260210-1.20260812.1.el9_8	4:20260210-1.20260812.1.el9_8
SUSE:Linux Enterprise Micro 5.3	ucode-intel	before 20260812-150200.68.1	20260812-150200.68.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	microcode_ctl	before 1.17-102.83.98.1	1.17-102.83.98.1
SUSE:Linux Enterprise Server 12 SP5-LTSS	ucode-intel	before 20260812-164.1	20260812-164.1
SUSE:Linux Micro 6.0	ucode-intel	before 20260812-1.1	20260812-1.1
SUSE:Linux Micro 6.1	ucode-intel	before 20260812-slfo.1.1_1.1	20260812-slfo.1.1_1.1
SUSE:Linux Micro 6.2	ucode-intel	before 20260812-160000.1.1	20260812-160000.1.1

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
almalinux:microcode_ctl	4:20260812-1.el8_10 · AlmaLinux:8	Package registry (OSV)
opensuse:ucode-intel	20260812-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
red hat:microcode_ctl	4:20260812-1.el8_10 · Red Hat:enterprise_linux:8::baseos	Package registry (OSV)
rocky linux:microcode_ctl	4:20260812-1.el8_10 · Rocky Linux:8	Package registry (OSV)
suse:microcode_ctl	1.17-102.83.98.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	Package registry (OSV)
suse:ucode-intel	20260812-1.1 · SUSE:Linux Micro 6.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

Intel® Vulnerability Disclosure Program Intigriti · disclosure only (VDP)

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

Someone with local access to the system can trigger it.
Administrator privileges are required.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality
Integrity
Availability

Attack vector: Local
Attack complexity: High
Privileges required: High
User interaction: None
Scope: X

Weakness class (CWE)

CWE-1260 · Improper Handling of Overlap Between Protected Memory Ranges

CVSS vector

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:46 PM UTC

For records you follow, these changes also arrive as notifications. →

References

intel.com/content/www/us/en/security-center/advisory/intel-sa-01379.html

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records

Noroxi analysis

No Noroxi analysis for this record yet

We use this product, ask for help

Data sources and verification

CNA: intel

CVE.org (CNA)Aug 12, 2026, 2:46 PM UTC
CISA ADPAug 12, 2026, 2:46 PM UTC
NVDSep 29, 2026, 11:10 AM UTC
FIRST EPSSOct 3, 2026, 12:00 AM UTC
OSV / GHSAOct 5, 2026, 3:22 AM UTC

Each line is when that source was last processed for this record.

You’re seeing every CVE. Add your stack to narrow the list down to the ones that affect you.

Add your stack