Skip to main content

Linux Kernel CVE-2026-64288

| EUVDEUVD-2026-49000 MEDIUM
NULL Pointer Dereference (CWE-476)
2026-07-25 Linux GHSA-3fq6-32px-rfvq
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
4.7 MEDIUM

Race condition between TLB invalidation and vCPU initialization requires precise timing, warranting AC:H; PR:L reflects required local KVM host access; only availability impacted via kernel panic.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
4.7 MEDIUM
AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat
5.5 MEDIUM
qualitative

Primary rating from NVD.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 13, 2026 - 15:26 vuln.today
CVSS changed
Aug 13, 2026 - 15:07 NVD
5.5 (MEDIUM)
Patch available
Jul 25, 2026 - 11:18 EUVD
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: arm64: nv: Avoid dereferencing NULL VNCR pseudo-TLB

VNCR TLB invalidation occurs from MMU notifiers or TLBI instructions, and either can race against a vcpu not being onlined yet (no pseudo-TLB allocated). Similarly, the TLB might be invalid, and the invalidation should be skipped in this case.

Both kvm_invalidate_vncr_ipa() and kvm_invalidate_vncr_va() are expected to perform the same checks, except that the latter doesn't check for the allocation and blindly dereferences the pointer.

Solve this by introducing a new iterator built on top of the usual kvm_for_each_vcpu() that checks for both of the above conditions, and convert the two users to it.

AnalysisAI

Null pointer dereference in the Linux kernel's KVM arm64 nested virtualization subsystem allows a local low-privileged attacker to crash the host kernel via a race condition in VNCR pseudo-TLB invalidation. The function kvm_invalidate_vncr_va() dereferences the VNCR pseudo-TLB pointer without first verifying allocation or validity, unlike its companion kvm_invalidate_vncr_ipa(). Exploitation results in a kernel panic that disrupts all virtual machines on the affected host; no public exploit has been identified at time of analysis, and EPSS of 0.21% (11th percentile) reflects minimal observed exploitation activity.

Technical ContextAI

The vulnerability resides in the KVM hypervisor's arm64 nested virtualization (NV) subsystem, specifically in the VNCR (Virtual Nested CPU Register) pseudo-TLB invalidation logic. CWE-476 (Null Pointer Dereference) is the root cause: kvm_invalidate_vncr_va() unconditionally dereferences the VNCR pseudo-TLB pointer, which may be NULL when a vCPU has not yet been onlined - meaning no pseudo-TLB buffer has been allocated for it. TLB invalidation is triggered asynchronously by MMU notifiers or explicit TLBI instructions, creating a window where the pointer can be NULL. The companion function kvm_invalidate_vncr_ipa() already performs the required NULL and validity checks; the omission in kvm_invalidate_vncr_va() is the gap. The fix introduces a dedicated iterator over kvm_for_each_vcpu() that validates both allocation status and TLB validity before proceeding, applied consistently to both invalidation paths. CPE data (cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*) confirms the upstream Linux kernel as the affected product, scoped to arm64 KVM with nested virtualization support compiled in.

RemediationAI

Apply the stable-tree fix commits available at https://git.kernel.org/stable/c/7c73a269a880b1399baacfb9d521415e6ef7ecc2, https://git.kernel.org/stable/c/5fd30133af864a1de0a0bd87d3fe3cf23205fbc7, and https://git.kernel.org/stable/c/4be6cbeb93d26994bd1827ddbce391e3c4395c8f. Per EUVD data, patched releases include Linux 6.18.39 and 7.1.4; distribution maintainers (Debian, Ubuntu, RHEL, SUSE) should be consulted for backported stable packages. As a compensating control where patching is not immediately possible, disabling KVM nested virtualization (removing or not loading the KVM NV module, or setting the appropriate kernel boot parameter) eliminates the vulnerable code path entirely; the trade-off is loss of nested VM functionality for any workloads relying on it. General kernel update procedures apply; a reboot is required for the fix to take effect.

Vendor StatusVendor

SUSE

Severity: Moderate
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

CVE-2026-64288 vulnerability details – vuln.today

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