Intel Xeon 6 processors SMM/TDX privileges management

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.41+ |
Summary
A vulnerability described as problematic has been identified in Intel Xeon 6 processors. The affected element is an unknown function of the component SMM/TDX. The manipulation results in privileges management. This vulnerability was named CVE-2025-31936. The attack needs to be approached locally. There is no available exploit.
Details
A vulnerability, which was classified as problematic, was found in Intel Xeon 6 processors (unknown version). Affected is an unknown code block of the component SMM/TDX. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is available at intel.com. This vulnerability is traded as CVE-2025-31936 since 04/10/2025. The exploitability is told to be easy. Local access is required to approach this attack. Additional levels of successful authentication are necessary for exploitation. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 08/11/2026). This vulnerability is assigned to T1068 by the MITRE ATT&CK project.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.intel.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.2
VulDB Temp Score: 4.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
04/10/2025 CVE reserved08/11/2026 Advisory disclosed
08/11/2026 VulDB entry created
08/11/2026 VulDB entry last update
Sources
Vendor: intel.comAdvisory: intel.com
Status: Confirmed
CVE: CVE-2025-31936 (🔒)
GCVE (CVE): GCVE-0-2025-31936
GCVE (VulDB): GCVE-100-388218
Entry
Created: 08/11/2026 19:13Changes: 08/11/2026 19:13 (52)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.