{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-63939","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-07-19T07:54:57.022Z","datePublished":"2026-07-19T14:55:35.743Z","dateUpdated":"2026-08-05T12:37:26.628Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-05T12:37:26.628Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SEV: Compute the correct max length of the in-GHCB scratch area\n\nWhen setting the length of the GHCB scratch area, and the area is in the\nGHCB shared buffer, set the effective length of the scratch area to the max\npossible size given the start of the guest-provided pointer, and the end of\nthe shared buffer.\n\nThe code was \"fine\" when first introduced, as KVM doesn't consult the\nlength of the buffer when emulating MMIO, because the passed in @len always\nspecifies the *max* size required.  But for PSC requests, the incoming @len\nis just the minimum length (to process the header), and KVM needs to know\nthe full size of the scratch area to avoid buffer overflows (spoiler alert).\n\nOpportunistically rename @len => @min_len to better reflect its role."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","baseScore":9.3,"baseSeverity":"CRITICAL"},"scenarios":[{"lang":"en","value":"AV:L - Exploitation requires code running inside an SEV-SNP KVM guest that issues a PSC VMGEXIT via the GHCB protocol; the vulnerable path is reached through the local VM/hypercall interface (SVM_EXIT_VMGEXIT), not via any network-facing protocol.\nAC:L - Once running in an SEV-SNP guest, the attacker fully controls the GHCB scratch GPA, PSC header indices, and entry contents, and can reliably trigger the bug without races or conditions outside their control.\nPR:N - No host privileges are required; a cloud tenant or any party able to run a malicious SEV-SNP guest VM can reach this code without host root or CAP_SYS_ADMIN in the host init namespace.\nUI:N - Exploitation requires no action from a victim user; the malicious guest triggers the vulnerability autonomously during PSC VMGEXIT processing.\nS:C - The flaw is in KVM host-side handling of guest VMGEXIT requests and enables out-of-bounds kernel access that crosses the guest-to-hypervisor security boundary, consistent with a VM escape primitive.\nC:H - The bug causes out-of-bounds reads of PSC entry structures beyond the computed scratch buffer length, which can leak kernel-mapped memory adjacent to the GHCB page.\nI:H - The kernel writes PSC completion data (entry cur_page and hdr.cur_entry) using attacker-controlled indices beyond the actual scratch buffer, enabling out-of-bounds writes exploitable for memory corruption.\nA:H - Out-of-bounds access within the host's GHCB mapping can corrupt adjacent memory and trigger kernel oopses or panics, and repeated exploitation can deny service to the host and other tenants."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["arch/x86/kvm/svm/sev.c"],"versions":[{"version":"9b54e248d2644be71cb394eb85f31ad99e023a05","lessThan":"6ca9400d36005ffdca25f80186bea781c7e1dc4c","status":"affected","versionType":"git"},{"version":"9b54e248d2644be71cb394eb85f31ad99e023a05","lessThan":"9f0a9e780f02c02d025a190f1885e1d1d73b87bd","status":"affected","versionType":"git"},{"version":"9b54e248d2644be71cb394eb85f31ad99e023a05","lessThan":"6644565527c4c5f507088b1c9ddf72de47790b68","status":"affected","versionType":"git"},{"version":"9b54e248d2644be71cb394eb85f31ad99e023a05","lessThan":"5867d7e202e09f037cefe77f7af4413c7c0fa088","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["arch/x86/kvm/svm/sev.c"],"versions":[{"version":"6.11","status":"affected"},{"version":"0","lessThan":"6.11","status":"unaffected","versionType":"semver"},{"version":"6.12.93","lessThanOrEqual":"6.12.*","status":"unaffected","versionType":"semver"},{"version":"6.18.35","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.0.12","lessThanOrEqual":"7.0.*","status":"unaffected","versionType":"semver"},{"version":"7.1","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.11","versionEndExcluding":"6.12.93"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.11","versionEndExcluding":"6.18.35"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.11","versionEndExcluding":"7.0.12"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.11","versionEndExcluding":"7.1"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/6ca9400d36005ffdca25f80186bea781c7e1dc4c"},{"url":"https://git.kernel.org/stable/c/9f0a9e780f02c02d025a190f1885e1d1d73b87bd"},{"url":"https://git.kernel.org/stable/c/6644565527c4c5f507088b1c9ddf72de47790b68"},{"url":"https://git.kernel.org/stable/c/5867d7e202e09f037cefe77f7af4413c7c0fa088"}],"title":"KVM: SEV: Compute the correct max length of the in-GHCB scratch area","x_generator":{"engine":"bippy-1.2.0"}}}}