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

KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR

KVM currently maps the L1 VNCR into the host stage-1 by relying entirely
on the permissions of the guest stage-1. At the same time, it is
entirely possible that the backing PFN is read-only (e.g. RO memslot),
meaning that the L1 VNCR should use at most a read-only mapping.

Cache the writability of the PFN in the VNCR TLB and use it to constrain
the resulting fixmap permissions. Promote VNCR permission faults to an
SEA in the case where the guest attempts to write to a read-only
endpoint. Conveniently, this also plugs a page leak found by Sashiko [*]
resulting from the early return for a read-only PFN.
Published: 2026-08-15
Score: 9 Critical
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Based on the description, it is inferred that the Linux kernel KVM driver for ARM64 mishandles the mapping of the L1 VNCR when the backing physical frame number is marked read‑only. Because the kernel relied only on guest stage‑1 permissions, a guest could trigger write attempts to a read‑only endpoint, resulting in an improper mapping that can lead to memory corruption or the exposure of host memory through early returns and page leaks. The flaw does not depend on a specific kernel configuration and thus applies to any KVM‑enabled environment that uses L1 VNCR with read‑only backing pages.

Affected Systems

Based on the description, it is inferred that the vulnerability affects the Linux kernel KVM subsystem on ARM64 architectures. Version information is not explicitly listed in the advisory, but the fix appears in recent kernel commits, so all current and older releases before the patch are potentially impacted.

Risk and Exploitability

Based on the description, it is inferred that the potential consequence is privilege escalation from the guest to the host or unintended data leakage. The CVSS score of 9 indicates a high severity, while the EPSS score of <1% suggests a low exploitation probability. The absence of the vulnerability from CISA KEV indicates that it is not widely known, but the risk remains significant for environments with untrusted virtual machines because the attack would require a vulnerable guest to trigger a permission fault through the L1 VNCR; sophisticated guests or compromised workloads could exploit this.

Generated by OpenCVE AI on August 22, 2026 at 06:53 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the host Linux kernel to a version that includes the commit fixing KVM arm64 L1 VNCR permission handling.
  • Verify that the hypervisor does not expose read‑only host memory to guests via L1 VNCR; disable or restrict VM extensions that provide such mappings.
  • Maintain tight access control by keeping guest firmware and kernel at fully patched levels and avoid using read‑only memslots that could be mis‑mapped in the host.

Generated by OpenCVE AI on August 22, 2026 at 06:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 19 Aug 2026 00:15:00 +0000

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

None

threat_severity

Moderate


Mon, 17 Aug 2026 19:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-284

Mon, 17 Aug 2026 17:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-284

Mon, 17 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

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


Sat, 15 Aug 2026 11:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-284

Sat, 15 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR KVM currently maps the L1 VNCR into the host stage-1 by relying entirely on the permissions of the guest stage-1. At the same time, it is entirely possible that the backing PFN is read-only (e.g. RO memslot), meaning that the L1 VNCR should use at most a read-only mapping. Cache the writability of the PFN in the VNCR TLB and use it to constrain the resulting fixmap permissions. Promote VNCR permission faults to an SEA in the case where the guest attempts to write to a read-only endpoint. Conveniently, this also plugs a page leak found by Sashiko [*] resulting from the early return for a read-only PFN.
Title KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR
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-08-17T05:42:14.902Z

Reserved: 2026-08-09T03:40:39.916Z

Link: CVE-2026-72279

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T06:21:58.077

Modified: 2026-08-17T06:18:30.473

Link: CVE-2026-72279

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-08-15T00:00:00Z

Links: CVE-2026-72279 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-22T07:00:07Z

Weaknesses
  • CWE-279

    Incorrect Execution-Assigned Permissions

  • CWE-284

    Improper Access Control