# CVE-2025-35979: Information disclosure in Intel(R) Processors > Unprivileged local attackers can exploit shared microarchitectural predictor state in Intel processors to disclose sensitive information from guest VMs. - **Severity:** Medium 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`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 12 May 2026 - **Updated:** 12 May 2026 - **Also known as:** ALPINE-CVE-2025-35979, BELL-CVE-2025-35979, DEBIAN-CVE-2025-35979, GHSA-f5vw-x3gp-vr4c, MGASA-2026-0161, OESA-2026-2458, OESA-2026-2459, OESA-2026-2460, OESA-2026-2461, OESA-2026-2529, SUSE-SU-2026:21725-1, SUSE-SU-2026:21897-1, SUSE-SU-2026:2963-1, SUSE-SU-2026:2981-1, SUSE-SU-2026:3124-1, UBUNTU-CVE-2025-35979, openSUSE-SU-2026:10783-1 ## What is CVE-2025-35979? CVE-2025-35979 is a medium-severity vulnerability in Intel(R) Processors, published on 12 May 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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. Weakness: CWE-1423 (Exposure of Sensitive Information caused by Shared Microarchitectural Predictor State that Influences Transient Execution) ## Which versions are affected by CVE-2025-35979? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ucode-intel` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 20260512-150200.65.1 | | `ucode-intel` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 20260512-150200.65.1 | | `ucode-intel` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 20260512-150200.65.1 | | `ucode-intel` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 20260512-150200.65.1 | | `ucode-intel` | SUSE:Linux Enterprise Micro 5.3 | All versions | 20260512-150200.65.1 | | `ucode-intel` | SUSE:Linux Enterprise Micro 5.4 | All versions | 20260512-150200.65.1 | | `ucode-intel` | SUSE:Linux Enterprise Micro 5.5 | All versions | 20260512-150200.65.1 | | `ucode-intel` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 20260512-150200.65.1 | | `microcode_ctl` | SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | All versions | 1.17-102.83.95.1 | | `ucode-intel` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 20260512-161.1 | | `ucode-intel` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 20260512-150200.65.1 | | `ucode-intel` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 20260512-150200.65.1 | | `ucode-intel` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 20260512-150200.65.1 | | `ucode-intel` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 20260512-161.1 | | `ucode-intel` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 20260512-150200.65.1 | | `ucode-intel` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 20260512-150200.65.1 | | `ucode-intel` | SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 20260512-150200.65.1 | | `ucode-intel` | openSUSE:Tumbleweed | All versions | 20260512-1.1 | ## How do I fix CVE-2025-35979? Apply the vendor's patch. ## Is CVE-2025-35979 being exploited? There is no known exploitation of CVE-2025-35979 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-35979 and fix it if it is affected. What it is: CVE-2025-35979 is a medium-severity vulnerability in Intel(R) Processors, published on 12 May 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-35979 in the wild and no public exploit code. Affected product: Intel(R) Processors. 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-35979/ (Markdown: https://insights.sbomify.com/CVE-2025-35979/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-35979 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-35979 - OSV: https://osv.dev/vulnerability/CVE-2025-35979 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-35979/ Summaries are generated and may contain mistakes; the official description above is the record.