cve.bz

CVE-2025-31938

4.3 mediumEPSS 0.09%

Medium (4.3). EPSS 0.09% estimated probability of exploitation activity in the next 30 days.

On this page
Insufficient granularity of access control in some subsystem for some Intel(R) Xeon(R) 6 Scalable processors with Intel(R) TDX may allow an information disclosure. Authorized adversary with an authenticated user combined with a high complexity attack may enable data exposure. 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 (none), integrity (none) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (high), integrity (none) and availability (none) impacts.

Severity

CVSS 4.0

4.3 medium
CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N
EPSS
0.09% (unchanged from 0.09% a week ago; 0.09% 30 days ago) estimated probability of exploitation activity in the next 30 days; 0th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-1220 Insufficient Granularity of Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-31938 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-31938?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-31938?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-31938 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12intel-microcodeno fix listedDEBIAN-CVE-2025-31938
Debian13intel-microcode3.20260925.1~deb13u1DEBIAN-CVE-2025-31938
Debian14intel-microcode3.20260925.1DEBIAN-CVE-2025-31938
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 5 moreintel-microcodeno fix listedUBUNTU-CVE-2025-31938
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 11 moreucode-intel20260812-150200.68.1SUSE-SU-2026:4025-1
SUSELinux Enterprise Server 11 SP4 LTSS EXTREME COREmicrocode_ctl1.17-102.83.98.1SUSE-SU-2026:4019-1
SUSELinux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5ucode-intel20260812-164.1SUSE-SU-2026:3917-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0ucode-intel20260812-160000.1.1SUSE-SU-2026:23602-1
SUSELinux Micro 6.0ucode-intel20260812-1.1SUSE-SU-2026:23449-1
SUSELinux Micro 6.1ucode-intel20260812-slfo.1.1_1.1SUSE-SU-2026:23539-1
SUSELinux Micro 6.2ucode-intel20260812-160000.1.1SUSE-SU-2026:23459-1
openSUSELeap 16.0ucode-intel20260812-160000.1.1openSUSE-SU-2026:21736-1
openSUSETumbleweeducode-intel20260812-1.1openSUSE-SU-2026:11599-1
Alpaquita23, 25, streamintel-ucodeno fix listedBELL-CVE-2025-31938

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Attack patterns (CAPEC)

  • CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs Likelihood: High · Severity: High
  • CAPEC-180 Exploiting Incorrectly Configured Access Control Security Levels Likelihood: High · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON