# CVE-2025-38560: x86/sev: Evict cache lines during SNP memory validation

> Attackers can exploit cache coherency flaws in AMD SEV-SNP guests to read sensitive memory data during page validation.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Aug 2025
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-66536, BELL-CVE-2025-38560, DEBIAN-CVE-2025-38560, GHSA-rcx5-mm72-w6xv, ROOT-OS-DEBIAN-11-CVE-2025-38560, ROOT-OS-DEBIAN-12-CVE-2025-38560, ROOT-OS-DEBIAN-13-CVE-2025-38560, ROOT-OS-UBUNTU-2204-CVE-2025-38560, ROOT-OS-UBUNTU-2404-CVE-2025-38560, UBUNTU-CVE-2025-38560

## What is CVE-2025-38560?

CVE-2025-38560 is a critical vulnerability in Debian Debian Linux, published on 19 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

x86/sev: Evict cache lines during SNP memory validation

An SNP cache coherency vulnerability requires a cache line eviction
mitigation when validating memory after a page state change to private.
The specific mitigation is to touch the first and last byte of each 4K
page that is being validated. There is no need to perform the mitigation
when performing a page state change to shared and rescinding validation.

CPUID bit Fn8000001F_EBX[31] defines the COHERENCY_SFW_NO CPUID bit
that, when set, indicates that the software mitigation for this
vulnerability is not needed.

Implement the mitigation and invoke it when validating memory (making it
private) and the COHERENCY_SFW_NO bit is not set, indicating the SNP
guest is vulnerable.

## Which versions are affected by CVE-2025-38560?

It affects 2 products.


Products: Debian Debian Linux, Linux kernel.

## How do I fix CVE-2025-38560?

Apply the vendor's patch.

## Is CVE-2025-38560 being exploited?

There is no known exploitation of CVE-2025-38560 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-38560 and fix it if it is affected.

What it is: CVE-2025-38560 is a critical vulnerability in Debian Debian Linux, published on 19 Aug 2025. 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-38560 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-38560/ (Markdown: https://insights.sbomify.com/CVE-2025-38560/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-38560
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-38560
- OSV: https://osv.dev/vulnerability/CVE-2025-38560

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-38560/
Summaries are generated and may contain mistakes; the official description above is the record.