Skip to main content

Linux Kernel EUVDEUVD-2026-48997

| CVE-2026-64285 MEDIUM
2026-07-25 Linux GHSA-9frv-wmxv-xpwj
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
5.5 MEDIUM

Local VMM process (PR:L) on AMD SEV-SNP hardware triggers host kernel panic via KVM write to read-only page; no confidentiality or integrity impact applies.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
SUSE
7.1 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

4
Analysis Generated
Aug 13, 2026 - 15:26 vuln.today
CVSS changed
Aug 13, 2026 - 15:07 NVD
5.5 (MEDIUM)
CVE Published
Jul 25, 2026 - 08:49 nvd
MEDIUM 5.5
CVE Published
Jul 25, 2026 - 08:49 cve.org
UNKNOWN (no severity yet)

DescriptionNVD

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

KVM: SEV: Pin source page for write when adding CPUID data for SNP guest

When populating a guest_memfd instance with the initial CPUID data for an SNP guest, acquire a writable pin on the source page as KVM will write back the "correct" CPUID information if the userspace provided data is rejected by trusted firmware. Because KVM writes to the source page using a kernel mapping, pinning for read could result in KVM clobbering read-only memory.

Note, well-behaved VMMs are unlikely to be affected, as CPUID information is almost always dynamically generated by userspace, i.e. it's unlikely for the CPUID information to be backed by a read-only mapping.

[sean: rewrite shortlog and changelog, tag for stable@]

AnalysisAI

KVM's SEV-SNP guest initialization path in the Linux kernel can trigger a host kernel panic when processing CPUID data backed by a read-only memory mapping. The flaw affects hypervisors running Linux 7.0.x before 7.1.4 where a local, low-privileged VMM process can cause KVM to write corrected CPUID values into a read-only source page after AMD's trusted firmware rejects the userspace-supplied data. No public exploit has been identified and EPSS sits at 0.20% (10th percentile), consistent with a niche, difficult-to-trigger local denial-of-service condition with no confirmed active exploitation.

Technical ContextAI

The vulnerability resides in the KVM (Kernel-based Virtual Machine) subsystem's handling of AMD SEV-SNP (Secure Encrypted Virtualization - Secure Nested Paging) guest initialization via the guest_memfd interface. When populating CPUID data for an SNP guest, KVM previously acquired only a read pin - not a writable pin - on the userspace-supplied source page. AMD's Secure Processor (trusted firmware) validates CPUID entries and can reject userspace-supplied values, upon which KVM writes back the authoritative corrected values directly to the source page via a kernel mapping. Using a read-only pin in this path allows KVM to overwrite read-only memory, producing a kernel oops or panic on the host. The CPE cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:* confirms the scope is the upstream Linux kernel. No CWE is assigned by NVD, but the root cause is closest to improper memory access rights enforcement - the kernel fails to verify write permissions on a page it subsequently writes to. The EUVD tags this as 'Information Disclosure,' which directly conflicts with the CVSS vector (C:N) and the description; the actual impact is host availability loss, not data exposure - this tag appears to be a classification error.

RemediationAI

Upgrade to Linux kernel 7.1.4 or later, or to 7.2-rc1 or later for mainline tracking. Two stable-tree backport commits are available and verifiable at https://git.kernel.org/stable/c/dcdb476f5fc5701ec06c23efe3e3529f07ca391e and https://git.kernel.org/stable/c/f13e900599089b10113ceb36013423f0837c6792. Distribution-specific kernel packages (RHEL, Ubuntu, SUSE, Debian) should be monitored for backported fixes; apply vendor kernel updates as they become available - no downstream distribution advisories are confirmed in the provided references. If immediate patching is not feasible, restrict access to /dev/kvm to trusted VMM processes only (via filesystem permissions or cgroup device access controls), reducing the privilege surface at the cost of preventing untrusted users from creating any KVM guests. Disabling SEV-SNP guest creation entirely via the BIOS/UEFI AMD SME/SEV settings or via the kernel boot parameter 'kvm_amd.sev=0' eliminates the vulnerable code path entirely, at the cost of losing confidential computing guest support on the host.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
openSUSE Tumbleweed Fixed
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected

Share

EUVD-2026-48997 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy