Skip to main content
VulnerabilityPublished Updated

CVE-2026-63937: Linux kernel · KVM: SEV: Use READ_ONCE() when reading entries/indices from PSC buffer

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High · fixed in edbbe88f83b524434974e84808d3093199d67c24 : patch Linux kernel soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in edbbe88f83b524434974e84808d3093199d67c24, c8cc238093ca6c99267032f6cfe78f59389f3157, bd232801ef1d1fd985d2d4ca3cd1d888303ca86f +1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Linux kernel to edbbe88f83b524434974e84808d3093199d67c24, c8cc238093ca6c99267032f6cfe78f59389f3157, bd232801ef1d1fd985d2d4ca3cd1d888303ca86f or b1dfaa6f7a957726a6800135be3659fbe4bbf2a4.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 9b54e248d2644be71cb394eb85f31ad99e023a05, < edbbe88f83b524434974e84808d3093199d67c24
Fixed in
  • edbbe88f83b524434974e84808d3093199d67c24
LinuxLinuxAffected
  • ≥ 9b54e248d2644be71cb394eb85f31ad99e023a05, < c8cc238093ca6c99267032f6cfe78f59389f3157
Fixed in
  • c8cc238093ca6c99267032f6cfe78f59389f3157
LinuxLinuxAffected
  • ≥ 9b54e248d2644be71cb394eb85f31ad99e023a05, < bd232801ef1d1fd985d2d4ca3cd1d888303ca86f
Fixed in
  • bd232801ef1d1fd985d2d4ca3cd1d888303ca86f
LinuxLinuxAffected
  • ≥ 9b54e248d2644be71cb394eb85f31ad99e023a05, < b1dfaa6f7a957726a6800135be3659fbe4bbf2a4
Fixed in
  • b1dfaa6f7a957726a6800135be3659fbe4bbf2a4
LinuxLinuxAffected
  • =6.11
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Use READ_ONCE() when reading entries/indices from PSC buffer Use READ_ONCE() when reading entries/indices from the guest-accessible Page State Change buffer to defend against TOCTOU bugs. Don't bother with READ_ONCE()/WRITE_ONCE() for cases where KVM is writing (and not consuming the result!), as the guest isn't supposed to touch the buffer while it's being processed. I.e. using READ_ONCE() is all about protecting against misbehaving guests.

References

Community reviews

Loading reviews…