CVE-2025-35979 json
Exposure of sensitive information caused by shared microarchitectural predictor state that influences transient execution for some Intel(R)…
published 5mo ago modified 26d ago also EUVD-2025-209791
- cvss
- 6.8
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 0%
- public exploits
- 0
- none known
Summary
Exposure of sensitive information caused by shared microarchitectural predictor state that influences transient execution for some Intel(R) Processors within VMX non-root (guest) operation may allow an information disclosure. Unprivileged software 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 without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (none) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (high), integrity (none) and availability (none) impacts.
Patch / fix
- intel-microcode Debian 14 3.20260925.1
debian advisories DEBIAN-CVE-2025-35979
- ucode-intel SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 20260812-160000.1.1
- ucode-intel SLES for SAP 15 SP6, SLES for SAP 15 SP5, SLES for SAP 15 SP4 +11 more 20260512-150200.65.1
- microcode_ctl SLES 11 SP4 LTSS EXTREME CORE 1.17-102.83.95.1
- ucode-intel SLES LTSS Extended Security 12 SP5, SLES 12 SP5-LTSS 20260512-161.1
suse advisories SUSE-SU-2026:23459-1SUSE-SU-2026:23602-1SUSE-SU-2026:3124-1SUSE-SU-2026:2981-1SUSE-SU-2026:2963-1
- ucode-intel openSUSE Leap 16.0 20260812-160000.1.1
- ucode-intel openSUSE Tumbleweed 20260512-1.1
opensuse advisories openSUSE-SU-2026:21736-1openSUSE-SU-2026:10783-1
- intel-ucode Alpine 3.24, Alpine 3.23, Alpine 3.22 +2 more 20260512-r0
alpine advisories ALPINE-CVE-2025-35979
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2025-35979 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-35979 updated cvss 5.6
kernel: Kernel: Information disclosure via shared microarchitectural predictor state in Intel(R) Processors
-
Red Hat Enterprise Linux 6 microcode_ctl Red Hat Enterprise Linux 7 microcode_ctl Red Hat Enterprise Linux 8 microcode_ctl Red Hat Enterprise Linux 9 microcode_ctl Red Hat Enterprise Linux 10 microcode_ctl Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9affected: workaround, no fix available “Fix deferred”
+1 more productsfewer
Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5mo ago
Exploit prediction
0.10% chance of exploitation in the next 30 days, higher than 0% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.8 | CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N |
| CNA | 4.0 | 6.8 | CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/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 |
Affected products
- n/a Intel(R) Processors
Classification
- Weakness
-
- CWE-1423 Exposure of Sensitive Information caused by Shared Microarchitectural Predictor State that Influences Transient Execution
References
Sources
- CVE List CVE-2025-35979
- NVD CVE-2025-35979
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.