CVE-2026-64283·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: KVM: guest_memfd: Treat memslot binding offset+size as unsigned values When binding a memslot to a guest_memfd file, treat the offset and size as unsigned values to fix a bug where the sum of the two can result in a false negative when checking for overflow against the size of the file. Passing unsigned values also avoids relying on somewhat obscure checks in other flows for safety, and tracks the offset and size as they are intended to be tracked, as unsigned values. On 64-bit kernels, the number of pages a memslot contains and thus the size (and offset) of its guest_memfd binding are unsigned 64-bit values. Taking the offset+size as an loff_t instead of a uoff_t inadvertently converts the unsigned value to a signed value if the offset and/or size is massive. Locally storing the offset and size as signed values is benign in and of itself (though even that is *extremely* difficult to discern), but operating on their sum is not. For the offset, KVM explicitly checks against a negative value, which might seem like a bug as KVM could incorrectly reject a legitimate binding, but that's not actually the case as KVM_CREATE_GUEST_MEMFD takes a signed value for its size, i.e. a would-be-negative offset is also greater than the maximum possible size of any guest_memfd file. Regarding the size, while KVM lacks an explicit check for a negative value, i.e. seemingly has a flawed overflow check, KVM restricts the number of pages in a single memslot to the largest positive signed 32-bit value: if (id < KVM_USER_MEM_SLOTS && (mem->memory_size >> PAGE_SHIFT) > KVM_MEM_MAX_NR_PAGES) return -EINVAL; and so that maximum "size" will ever be is 0x7fffffff000. The sum of the two is, however, problematic. While the size is restricted by KVM's memslot logic, the offset is not, i.e. the offset is completely unchecked until the "offset + size > i_size_read(inode)" check. If the offset is the (nearly) largest possible _positive_ value, then adding size to the offset can result in a signed, negative 64-bit value. When compared against the size of the file (guaranteed to be positive), the negative sum is always smaller, and KVM incorrectly allows the absurd offset. Opportunistically add missing includes in kvm_mm.h (instead of relying on its parents).
- Severity
- high
- Software
- Kernel
- Fixed in
- 7.1.4
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.14% — higher than 3% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-64283 scores 7 on CVSS, so a successful attack would be serious — but at 0.14%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.8
Until: 7.1.4
Fixed in: 7.1.4
How to fix this CVE
Update your Linux kernel to version 7.1.4 or later to resolve a memory binding calculation flaw in KVM's guest_memfd implementation. This vulnerability allows incorrect validation of guest memory file offsets when combined with size values, potentially leading to unauthorized memory access. Kernel versions 6.8 through 7.1.3 require patching; verify your current version and apply available security updates immediately.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Check kernel version: uname -r (confirm it is 7.1.4 or later; vulnerable range is 6.8.x to 7.1.3)
- Verify KVM is enabled: grep -i kvm /proc/cpuinfo (presence indicates KVM capability; if absent, vulnerability is not exposed)
- Check for guest_memfd usage: ps aux | grep -i qemu or virsh list --all (active VMs using guest_memfd are at risk)
- Confirm patch applied: grep -i 'guest_memfd.*unsigned' /boot/config-$(uname -r) or compare kernel build date against CVE-2026-64283 fix date (June 2024 or later)
FAQ
What is CVE-2026-64283?
CVE-2026-64283 is a kernel vulnerability in KVM's guest_memfd memory binding logic where offset and size calculations are incorrectly treated as signed values instead of unsigned, allowing false validation checks that permit out-of-bounds memory access in virtualized environments.
Is CVE-2026-64283 being actively exploited?
No, CVE-2026-64283 is not currently listed in CISA's Known Exploited Vulnerabilities catalog, and no public exploits are available; however, it remains a high-severity flaw requiring patching due to its memory access implications.
What versions of Kernel are affected by CVE-2026-64283?
Linux kernel versions 6.8 through 7.1.3 are vulnerable; version 7.1.4 and later contain the fix.
How do I check if my server is vulnerable to CVE-2026-64283?
Run 'uname -r' and compare the output against version 7.1.4; if your version is 6.8 or later but prior to 7.1.4, you are vulnerable. Additionally, check 'grep -i kvm /proc/cpuinfo' to confirm KVM is enabled on your system.
Does Defensia detect CVE-2026-64283?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2026-64283 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-64283. Free for 1 server.
Get started free