In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Compute the correct max length of the in-GHCB scratch area When… (CVE-2026-63939)
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 => @min_len to better reflect its role.
AI Analysis
Technical Summary
The Linux kernel's KVM SEV component had a vulnerability where the maximum length of the in-GHCB scratch area was not correctly computed. Initially, the length parameter was used as the maximum size for MMIO emulation, which was safe. However, for PSC requests, the length parameter represented only the minimum required size, causing KVM to underestimate the scratch area size and potentially leading to buffer overflows. The patch corrects this by setting the effective length to the maximum possible size between the guest pointer and the end of the shared buffer, preventing overflow conditions.
Potential Impact
This vulnerability could allow a buffer overflow in the KVM SEV GHCB scratch area handling, potentially leading to memory corruption within the virtualized environment. No known exploits are reported in the wild. The impact is limited to environments using KVM with SEV and GHCB features.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel. Users should apply the official kernel updates that include this patch to ensure the correct computation of the GHCB scratch area length and prevent buffer overflows. Since this is a kernel-level issue, updating to a patched kernel version is the recommended remediation. Patch status is not explicitly stated in the provided data; users should consult the Linux kernel vendor advisory for the exact fixed versions and update accordingly.
In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Compute the correct max length of the in-GHCB scratch area When… (CVE-2026-63939)
Description
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 => @min_len to better reflect its role.
CVSS v3.1
Score 9.3critical
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's KVM SEV component had a vulnerability where the maximum length of the in-GHCB scratch area was not correctly computed. Initially, the length parameter was used as the maximum size for MMIO emulation, which was safe. However, for PSC requests, the length parameter represented only the minimum required size, causing KVM to underestimate the scratch area size and potentially leading to buffer overflows. The patch corrects this by setting the effective length to the maximum possible size between the guest pointer and the end of the shared buffer, preventing overflow conditions.
Potential Impact
This vulnerability could allow a buffer overflow in the KVM SEV GHCB scratch area handling, potentially leading to memory corruption within the virtualized environment. No known exploits are reported in the wild. The impact is limited to environments using KVM with SEV and GHCB features.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel. Users should apply the official kernel updates that include this patch to ensure the correct computation of the GHCB scratch area length and prevent buffer overflows. Since this is a kernel-level issue, updating to a patched kernel version is the recommended remediation. Patch status is not explicitly stated in the provided data; users should consult the Linux kernel vendor advisory for the exact fixed versions and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-94xr-m4g8-q6cc
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63939"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- 3.1
Threat ID: 6a5d27aa2a4a8d598912ebcb
Added to database: 07/19/2026, 19:38:18 UTC
Last enriched: 07/19/2026, 20:05:38 UTC
Last updated: 09/01/2026, 10:52:10 UTC
Views: 76
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.