Nixpkgs security tracker

Login with GitHub

Suggestion detail

Dismissed
(max. allowed matches exceeded)
Permalink CVE-2026-63937
8.8 HIGH
  • CVSS version (CVSS): 3.1
  • Attack Vector (AV): Local (L)
  • Attack Complexity (AC): Low (L)
  • Privileges Required (PR): Low (L)
  • User Interaction (UI): None (N)
  • Scope (S): Changed (C)
  • Confidentiality (C): High (H)
  • Integrity (I): High (H)
  • Availability (A): High (H)
  • Modified Attack Vector (MAV): Local (L)
  • Modified Attack Complexity (MAC): Low (L)
  • Modified Privileges Required (MPR): Low (L)
  • Modified User Interaction (MUI): None (N)
  • Modified Confidentiality (MC): High (H)
  • Modified Scope (MS): Changed (C)
  • Modified Integrity (MI): High (H)
  • Modified Availability (MA): High (H)
created 6 days, 1 hour ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
KVM: SEV: Use READ_ONCE() when reading entries/indices from PSC buffer

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.

Affected products

Linux
  • <edbbe88f83b524434974e84808d3093199d67c24
  • <b1dfaa6f7a957726a6800135be3659fbe4bbf2a4
  • =<6.18.*
  • =<7.0.*
  • =<6.12.*
  • <6.11
  • =<*
  • <bd232801ef1d1fd985d2d4ca3cd1d888303ca86f
  • ==6.11
  • <c8cc238093ca6c99267032f6cfe78f59389f3157