CVE-2026-63939: KVM: SEV: Compute the correct max length of the in-GHCB scratch area
In the Linux kernel, the following vulnerability has been resolved:
KVM: SEV: Compute the correct max length of the in-GHCB scratch area
When setting the length of the GHCB scratch area, and the area is in the GHCB shared buffer, set the effective length of the scratch area to the max possible size given the start of the guest-provided pointer, and the end of the shared buffer.
The code was "fine" when first introduced, as KVM doesn't consult the length of the buffer when emulating MMIO, because the passed in @len always specifies the max size required. But for PSC requests, the incoming @len is just the minimum length (to process the header), and KVM needs to know the full size of the scratch area to avoid buffer overflows (spoiler alert).
Opportunistically rename @len => @minlen to better reflect its role.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-63939?
CVE-2026-63939 has a critical severity rating of 9.3.
What is the risk level associated with CVE-2026-63939?
CVE-2026-63939 has a risk level of 77.
How do I fix CVE-2026-63939?
To fix CVE-2026-63939, update your Linux kernel to the version that resolves this vulnerability.
What type of vulnerability is CVE-2026-63939?
CVE-2026-63939 is a buffer overflow vulnerability.
Which software is affected by CVE-2026-63939?
CVE-2026-63939 affects the Linux kernel.