Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

CriticalCVSS 9.3 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 37/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 5867d7e202e09f037cefe77f7af4413c7c0fa088, 6644565527c4c5f507088b1c9ddf72de47790b68, 6ca9400d36005ffdca25f80186bea781c7e1dc4c.

Low priority for now. Upgrade to Linux Linux 5867d7e202e09f037cefe77f7af4413c7c0fa088, 6644565527c4c5f507088b1c9ddf72de47790b68, 6ca9400d36005ffdca25f80186bea781c7e1dc4c or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Jul 19, 2026
Updated
Oct 28, 2026
EPSS
0.2% · 10th percentile

Report tools

JSON

Action score

37

Monitor

Low priority for now.

CVSS
37 / 40 · 9.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
9.3
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-63939

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.11affected
    • 9b54e248d2644be71cb394eb85f31ad99e023a05 and later · before 6ca9400d36005ffdca25f80186bea781c7e1dc4caffected · git
    • 9b54e248d2644be71cb394eb85f31ad99e023a05 and later · before 9f0a9e780f02c02d025a190f1885e1d1d73b87bdaffected · git
    • 9b54e248d2644be71cb394eb85f31ad99e023a05 and later · before 6644565527c4c5f507088b1c9ddf72de47790b68affected · git
    • 9b54e248d2644be71cb394eb85f31ad99e023a05 and later · before 5867d7e202e09f037cefe77f7af4413c7c0fa088affected · git
    • before 6.11not affected · semver
    • 6.12.93 and later · up to and including 6.12.*not affected · semver
    • 6.18.35 and later · up to and including 6.18.*not affected · semver
    • 7.0.12 and later · up to and including 7.0.*not affected · semver
    • 7.1 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.12.94-16.12.94-1
Debian:14linuxbefore 7.0.12-17.0.12-1
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_10before 11-150700.2.111-150700.2.1
SUSE:Linux Micro 6.2kernel-livepatch-SLE16_Update_0before 20-160000.4.320-160000.4.3
SUSE:Linux Micro 6.2kernel-livepatch-SLE16_Update_1before 18-160000.1.118-160000.1.1
SUSE:Linux Micro 6.2kernel-livepatch-SLE16_Update_10before 9-160000.1.19-160000.1.1
SUSE:Linux Micro 6.2kernel-livepatch-SLE16_Update_11before 9-160000.1.19-160000.1.1
SUSE:Linux Micro 6.2kernel-livepatch-SLE16_Update_12before 7-160000.1.17-160000.1.1
SUSE:Linux Micro 6.2kernel-livepatch-SLE16_Update_13before 7-160000.1.27-160000.1.2
SUSE:Linux Micro 6.2kernel-livepatch-SLE16_Update_2before 16-160000.1.116-160000.1.1
SUSE:Linux Micro 6.2kernel-livepatch-SLE16_Update_3before 15-160000.1.115-160000.1.1
SUSE:Linux Micro 6.2kernel-livepatch-SLE16_Update_4before 14-160000.1.114-160000.1.1
SUSE:Linux Micro 6.2kernel-livepatch-SLE16_Update_5before 13-160000.1.113-160000.1.1
SUSE:Linux Micro 6.2kernel-livepatch-SLE16_Update_6before 12-160000.1.112-160000.1.1
SUSE:Linux Micro 6.2kernel-livepatch-SLE16_Update_7before 11-160000.1.111-160000.1.1
SUSE:Linux Micro 6.2kernel-livepatch-SLE16_Update_8before 10-160000.1.110-160000.1.1
SUSE:Linux Micro 6.2kernel-livepatch-SLE16_Update_9before 9-160000.1.19-160000.1.1
SUSE:Linux Micro 6.2kernel-livepatch-SLE16-RT_Update_0before 18-160000.3.418-160000.3.4
SUSE:Linux Micro 6.2kernel-livepatch-SLE16-RT_Update_1before 17-160000.1.117-160000.1.1
SUSE:Linux Micro 6.2kernel-livepatch-SLE16-RT_Update_10before 9-160000.1.19-160000.1.1
SUSE:Linux Micro 6.2kernel-livepatch-SLE16-RT_Update_11before 9-160000.1.19-160000.1.1
SUSE:Linux Micro 6.2kernel-livepatch-SLE16-RT_Update_12before 7-160000.1.17-160000.1.1
SUSE:Linux Micro 6.2kernel-livepatch-SLE16-RT_Update_13before 7-160000.1.17-160000.1.1
SUSE:Linux Micro 6.2kernel-livepatch-SLE16-RT_Update_2before 15-160000.1.115-160000.1.1

+7

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-63937Jul 19, 2026 · KVM: SEV: Use READ_ONCE() when reading entries/indices from PSC buffer
    35Monitor
  • ← EarlierCVE-2026-63938Jul 19, 2026 · KVM: SEV: Check PSC request indices against the actual size of the buffer
    37Monitor
  • Later →CVE-2026-63940Jul 19, 2026 · KVM: SEV: Ignore Port I/O requests of length '0'
    37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux5867d7e202e09f037cefe77f7af4413c7c0fa088Vendor (CNA)
Linux Linux6644565527c4c5f507088b1c9ddf72de47790b68Vendor (CNA)
Linux Linux6ca9400d36005ffdca25f80186bea781c7e1dc4cVendor (CNA)
Linux Linux9f0a9e780f02c02d025a190f1885e1d1d73b87bdVendor (CNA)
debian:linux6.12.94-1 · Debian:13Package registry (OSV)
suse:kernel-livepatch-SLE15-SP7-RT_Update_1011-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_117-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_109-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_119-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_127-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_137-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_215-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_314-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_414-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_513-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_612-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_711-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_99-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-6455810 days aparts390/pkey: Check length in pkey_pckmo handler implementation
    31Monitor
  • CVE-2026-4332972 days apartnetfilter: flowtable: strictly check for maximum number of actions
    31Monitor
  • CVE-2026-645246 days apartdrm/hyperv: validate resolution_count and fix WIN8 fallback
    30Monitor

Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

References

All records