Skip to content
Fencer Intel
critical 9.3

CVE-2026-63939 in the critical feed json

KVM: SEV: Compute the correct max length of the in-GHCB scratch area

published 3mo ago modified 14d ago also EUVD-2026-45712

cvss
9.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 10%
public exploits
0
none known

Summary

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.

Patch / fix

  • Linux Linux 6.12.93, 6.18.35, 7.0.12, 7.1
  • linux Debian 13 6.12.94-1
  • linux Debian 14 7.0.12-1

debian advisories DEBIAN-CVE-2026-63939

  • linux Ubuntu 26.04 LTS 7.0.0-28.28
  • linux-aws Ubuntu 26.04 LTS 7.0.0-1009.9
  • linux-gcp Ubuntu 26.04 LTS 7.0.0-1008.8
  • linux-gke Ubuntu 26.04 LTS 7.0.0-1003.4
  • linux-ibm Ubuntu 26.04 LTS 7.0.0-1010.10
  • linux-azure Ubuntu 26.04 LTS 7.0.0-1010.10
  • linux-raspi Ubuntu 26.04 LTS 7.0.0-1015.15
  • linux-riscv Ubuntu 26.04 LTS 7.0.0-28.28.1

ubuntu advisories UBUNTU-CVE-2026-63939

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-livepatch-SLE16_Update_10 SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 9-160000.1.1
  • kernel-livepatch-SLE16_Update_1 SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 18-160000.1.1
  • kernel-livepatch-SLE16_Update_5 SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 13-160000.1.1
  • kernel-livepatch-SLE16_Update_8 SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 10-160000.1.1
  • kernel-livepatch-SLE16_Update_11 SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 9-160000.1.1
  • kernel-livepatch-SLE16_Update_0 SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 20-160000.4.3
  • kernel-livepatch-SLE16_Update_2 SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 16-160000.1.1
  • kernel-livepatch-SLE16_Update_6 SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 12-160000.1.1

suse advisories SUSE-SU-2026:24431-1SUSE-SU-2026:24455-1SUSE-SU-2026:24434-1SUSE-SU-2026:24458-1SUSE-SU-2026:24433-1SUSE-SU-2026:24457-1

  • kernel-rt openSUSE Leap 16.0 6.12.0-160000.37.1
  • dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.37.1
  • kernel-64kb openSUSE Leap 16.0 6.12.0-160000.37.1
  • kernel-syms openSUSE Leap 16.0 6.12.0-160000.37.1
  • kernel-azure openSUSE Leap 16.0 6.12.0-160000.37.1
  • kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.37.1
  • kernel-source openSUSE Leap 16.0 6.12.0-160000.37.1
  • kernel-default openSUSE Leap 16.0 6.12.0-160000.37.1

opensuse advisories openSUSE-SU-2026:21555-1

Is CVE-2026-63939 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-63939 updated cvss 7.0

kernel: KVM: SEV: Compute the correct max length of the in-GHCB scratch area

  • Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +82 more Red Hat Enterprise Linux 10 kernel
    affected: workaround, no fix available
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 kernel-rt, kernel-rt-selftests-internal
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
26d ago

Exploit prediction

0.20% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 9.3 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected products

  • Linux Linux

Classification

Weakness
  • CWE-122 Heap-based Buffer Overflow
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.