In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: nv: Avoid dereferencing NULL VNCR pseudo-TLB VNCR TLB invalidation… (CVE-2026-64288)
A vulnerability in the Linux kernel's KVM arm64 virtualization code involving dereferencing a NULL VNCR pseudo-TLB pointer has been resolved. The issue arises from a race condition where TLB invalidation can occur before a virtual CPU is fully initialized, leading to a NULL pointer dereference. The fix introduces a new iterator that properly checks for allocation before dereferencing pointers during TLB invalidation.
AI Analysis
Technical Summary
CVE-2026-64288 addresses a vulnerability in the Linux kernel's KVM arm64 subsystem where VNCR TLB invalidation functions could dereference a NULL pointer due to a race condition between MMU notifiers or TLBI instructions and the vCPU initialization state. Specifically, the function kvm_invalidate_vncr_va() did not check for allocation before dereferencing, unlike kvm_invalidate_vncr_ipa(). The patch introduces a new iterator that performs necessary checks to avoid NULL pointer dereferences during TLB invalidation.
Potential Impact
The vulnerability could cause kernel crashes or instability due to NULL pointer dereferences during virtual CPU initialization and TLB invalidation. There is no information about exploitation in the wild or further impact such as privilege escalation or code execution.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by adding proper checks before dereferencing pointers during TLB invalidation. Users should apply the official kernel updates containing this fix when available. Patch status is not explicitly confirmed in the provided data; check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: nv: Avoid dereferencing NULL VNCR pseudo-TLB VNCR TLB invalidation… (CVE-2026-64288)
Description
A vulnerability in the Linux kernel's KVM arm64 virtualization code involving dereferencing a NULL VNCR pseudo-TLB pointer has been resolved. The issue arises from a race condition where TLB invalidation can occur before a virtual CPU is fully initialized, leading to a NULL pointer dereference. The fix introduces a new iterator that properly checks for allocation before dereferencing pointers during TLB invalidation.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-64288 addresses a vulnerability in the Linux kernel's KVM arm64 subsystem where VNCR TLB invalidation functions could dereference a NULL pointer due to a race condition between MMU notifiers or TLBI instructions and the vCPU initialization state. Specifically, the function kvm_invalidate_vncr_va() did not check for allocation before dereferencing, unlike kvm_invalidate_vncr_ipa(). The patch introduces a new iterator that performs necessary checks to avoid NULL pointer dereferences during TLB invalidation.
Potential Impact
The vulnerability could cause kernel crashes or instability due to NULL pointer dereferences during virtual CPU initialization and TLB invalidation. There is no information about exploitation in the wild or further impact such as privilege escalation or code execution.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by adding proper checks before dereferencing pointers during TLB invalidation. Users should apply the official kernel updates containing this fix when available. Patch status is not explicitly confirmed in the provided data; check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-3fq6-32px-rfvq
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64288"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420e9c2644c7f80865f3
Added to database: 07/25/2026, 23:09:02 UTC
Last enriched: 07/25/2026, 23:40:52 UTC
Last updated: 07/26/2026, 03:59:05 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.