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

KVM: SEV: Do cache maintenance on the source VM during intra-host migration

Manually perform cache maintenance on the source VM during intra-host
migration to ensure no stale data is left in CPU caches after the VM is
destroyed. Because the source VM is "converted" to a non-SEV VM, KVM's
memory reclaim flows won't trigger cache maintenance, e.g. when all guest
memory is reclaimed in response to detaching from the mmu_notifier.

Note, relying on the destination VM to do cache maintenance isn't an option
as KVM doesn't require identical guest memory configurations, i.e. the
source VM may have access to memory that the destination VM does not.
Enforcing equivalent memory configurations is infeasible, as it would
require a *deep* comparison of memslots, e.g. to verify that not only are
the memslot identical, but what the memslots point at is also identical.
Published: 2026-10-18
Score: 7.1 High
EPSS: < 1% Very Low
KEV: No
Impact: Potential data leakage from stale CPU caches
Action: Apply patch
AI Analysis

Impact

During an intra‑host migration of a KVM guest that utilizes SEV, the Linux kernel does not issue cache maintenance on the source virtual machine after it is converted to a non‑SEV guest. This omission can leave sensitive data in host CPU caches that were encrypted for the guest, and an attacker could potentially read those stale cache lines. The weakness is a missing cache‑flush step that allows privacy disclosure.

Affected Systems

The defect is present in all Linux kernels that include KVM SEV migration code and have not been patched to add cache maintenance on the source VM during migration. No specific kernel version range is listed, so any distribution shipping an unpatched kernel that contains the SEV migration code is potentially affected.

Risk and Exploitability

The CVSS score of 7.1 and an EPSS score < 1% indicate high severity and a low likelihood of exploitation yet. The vulnerability is not listed in CISA KEV, suggesting no publicly known exploits. The attack requires a privileged host operator or an attacker able to co‑locate a malicious guest and trigger a migration, as inferred from the description. The risk is primarily to data confidentiality for sensitive information that may have been cached during the VM’s execution.

Generated by OpenCVE AI on October 24, 2026 at 15:49 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply a patched Linux kernel that adds cache maintenance during SEV migration
  • If a patch cannot be applied immediately, disable SEV migration or prevent intra‑host migrations of SEV guests
  • If disabling migration is not possible, manually clear the host CPU caches after each SEV migration, for example by running a privileged cache‑flush command

Generated by OpenCVE AI on October 24, 2026 at 15:49 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 24 Oct 2026 14:15:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 5.6, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N'}

cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H'}


Tue, 20 Oct 2026 12:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-459
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.6, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N'}

threat_severity

Moderate


Sun, 18 Oct 2026 15:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Do cache maintenance on the source VM during intra-host migration Manually perform cache maintenance on the source VM during intra-host migration to ensure no stale data is left in CPU caches after the VM is destroyed. Because the source VM is "converted" to a non-SEV VM, KVM's memory reclaim flows won't trigger cache maintenance, e.g. when all guest memory is reclaimed in response to detaching from the mmu_notifier. Note, relying on the destination VM to do cache maintenance isn't an option as KVM doesn't require identical guest memory configurations, i.e. the source VM may have access to memory that the destination VM does not. Enforcing equivalent memory configurations is infeasible, as it would require a *deep* comparison of memslots, e.g. to verify that not only are the memslot identical, but what the memslots point at is also identical.
Title KVM: SEV: Do cache maintenance on the source VM during intra-host migration
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-24T14:09:00.765Z

Reserved: 2026-09-25T10:25:14.351Z

Link: CVE-2026-98471

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-18T16:16:57.600

Modified: 2026-10-24T14:16:43.463

Link: CVE-2026-98471

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-10-18T00:00:00Z

Links: CVE-2026-98471 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-24T16:00:18Z

Weaknesses