Lucene search
+L

340 matches found

RedhatCVE
RedhatCVE
•added 2026/07/21 9:50 p.m.•17 views

CVE-2026-63937

A flaw was found in the Linux kernel's Kernel-based Virtual Machine KVM with Secure Encrypted Virtualization SEV. This time-of-check to time-of-use TOCTOU vulnerability exists when KVM processes the guest-accessible Page State Change PSC buffer. A misbehaving guest could exploit this timing issue...

8.8CVSS5.7AI score0.00175EPSS
SaveExploits0References4
SUSE CVE
SUSE CVE
•added 2026/07/21 1:03 p.m.•20 views

SUSE CVE-2026-63940

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Ignore Port I/O requests of length '0' Explicitly ignore Port I/O requests of length '0' or count '0', so that setting up the software scratch area and other code doesn't have to worry about underflowing the length, and...

5.8CVSS5.7AI score0.00196EPSS
SaveExploits0References17
Tenable Nessus
Tenable Nessus
•added 2026/07/20 12:00 a.m.•18 views

Linux Distros Unpatched Vulnerability : CVE-2026-63940

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - KVM: SEV: Ignore Port I/O requests of length '0' Explicitly ignore Port I/O requests of length '0' or count '0', so that setting up the software scratch area an...

9.3CVSS5.7AI score0.00196EPSS
SaveExploits0References4
NVD
NVD
•added 2026/07/19 4:17 p.m.•19 views

CVE-2026-63938

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Check PSC request indices against the actual size of the buffer When processing Page State Change PSC requests, validate the PSC buffer against the effective size of the scratch area, which could be less than the maximu...

9.3CVSS0.00196EPSS
SaveExploits0References4
NVD
NVD
•added 2026/07/19 4:17 p.m.•22 views

CVE-2026-63939

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 si...

9.3CVSS0.00212EPSS
SaveExploits0References4
Debian CVE
Debian CVE
•added 2026/07/19 3:39 p.m.•19 views

CVE-2026-64018

In the Linux kernel, the following vulnerability has been resolved: net: mana: validate rxreqidx to prevent out-of-bounds array access In manahwcrxeventhandler, rxreqidx is derived from sge-address in DMA-coherent memory. In Confidential VMs SEV-SNP/TDX, this memory is shared unencrypted and HW c...

9.3CVSS5.9AI score0.00142EPSS
SaveExploits0
EUVD
EUVD
•added 2026/07/19 2:55 p.m.•23 views

EUVD-2026-45713

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Ignore Port I/O requests of length '0' Explicitly ignore Port I/O requests of length '0' or count '0', so that setting up the software scratch area and other code doesn't have to worry about underflowing the length, and...

5.7AI score0.00196EPSS
SaveExploits0References4
Cvelist
Cvelist
•added 2026/07/19 2:55 p.m.•48 views

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

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 si...

9.3CVSS0.00212EPSS
SaveExploits0References4
CVE
CVE
•added 2026/07/19 2:55 p.m.•64 views

CVE-2026-63939

CVE-2026-63939 (Linux kernel, KVM SEV): The issue concerns computation of the maximum length for the in-GHCB scratch area in the GHCB shared buffer. Previously, KVM assumed the input length (@len) always represented the maximum required size for MMIO emulation; for PSC requests, @len is only the ...

9.3CVSS5.9AI score0.00212EPSS
SaveExploits0References4
CVE
CVE
•added 2026/07/19 2:55 p.m.•52 views

CVE-2026-63938

The vulnerability CVE-2026-63938 affects the Linux kernel KVM SEV path, specifically PSC processing. The issue arises when validating PSC requests: the PSC buffer must be checked against the effective size of the scratch area, which may be smaller than the maximum if a guest supplies a pointer no...

9.3CVSS5.8AI score0.00196EPSS
SaveExploits0References4
CVE
CVE
•added 2026/07/19 2:55 p.m.•50 views

CVE-2026-63937

In the Linux kernel, CVE-2026-63937 pertains to KVM SEV where entries/indices in the guest-accessible PSC Page State Change buffer are now read with READ_ONCE() to defend against TOCTOU bugs. This change targets misbehavior by guests and reduces potential timing-related issues when the buffer is ...

8.8CVSS5.9AI score0.00175EPSS
SaveExploits0References4
OSV
OSV
•added 2026/07/19 2:55 p.m.•16 views

CVE-2026-63937 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 READONCE when reading entries/indices from PSC buffer Use READONCE when reading entries/indices from the guest-accessible Page State Change buffer to defend against TOCTOU bugs. Don't bother with READONCE/WRITEONCE...

8.8CVSS5.5AI score
SaveExploits0References7
Positive Technologies
Positive Technologies
•added 2026/07/19 12:00 a.m.•24 views

PT-2026-61256

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the KVM SEV implementation regarding the calculation of the maximum length of the in-GHCB scratch area. When the scratch area is located within the GHCB shared buffer,...

9.3CVSS5.7AI score0.00212EPSS
SaveExploits0
UbuntuCve
UbuntuCve
•added 2026/07/04 12:17 p.m.•22 views

CVE-2026-53360

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Require in-GHCB scratch area if GHCB v2+ is in use As per the GHCB spec, when using GHCB v2+ require the software scratch area to reside in the GHCB's shared buffer. Note, things like Page State Change PSC requests rely...

8.8CVSS6.6AI score0.00243EPSS
SaveExploits0References17
OSV
OSV
•added 2026/07/04 12:17 p.m.•19 views

UBUNTU-CVE-2026-53360

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Require in-GHCB scratch area if GHCB v2+ is in use As per the GHCB spec, when using GHCB v2+ require the software scratch area to reside in the GHCB's shared buffer. Note, things like Page State Change PSC requests rely...

8.8CVSS6.7AI score0.00243EPSS
SaveExploits0References18
Cvelist
Cvelist
•added 2026/07/04 11:53 a.m.•65 views

CVE-2026-53360 KVM: SEV: Require in-GHCB scratch area if GHCB v2+ is in use

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Require in-GHCB scratch area if GHCB v2+ is in use As per the GHCB spec, when using GHCB v2+ require the software scratch area to reside in the GHCB's shared buffer. Note, things like Page State Change PSC requests rely...

8.8CVSS0.00243EPSS
SaveExploits0References4
Debian CVE
Debian CVE
•added 2026/07/04 11:53 a.m.•18 views

CVE-2026-53360

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Require in-GHCB scratch area if GHCB v2+ is in use As per the GHCB spec, when using GHCB v2+ require the software scratch area to reside in the GHCB's shared buffer. Note, things like Page State Change PSC requests rely...

8.8CVSS6.7AI score0.00243EPSS
SaveExploits0
UbuntuCve
UbuntuCve
•added 2026/07/01 2:16 p.m.•22 views

CVE-2026-53345

In the Linux kernel, the following vulnerability has been resolved: KVM: Don't WARN if memory is dirtied without a vCPU when the VM is dying When marking a page dirty, complain about not having a running/loaded vCPU if and only if the VM is still alive, i.e. its refcount is non-zero. This will...

5.5CVSS5.5AI score0.0012EPSS
SaveExploits0References18
attackerkb
attackerkb
•added 2026/07/01 1:32 p.m.•12 views

CVE-2026-53345

In the Linux kernel, the following vulnerability has been resolved: KVM: Don't WARN if memory is dirtied without a vCPU when the VM is dying When marking a page dirty, complain about not having a running/loaded vCPU if and only if the VM is still alive, i.e. its refcount is non-zero. This will...

5.5AI score0.0012EPSS
SaveExploits0References6Affected Software1
OSV
OSV
•added 2026/07/01 1:32 p.m.•14 views

CVE-2026-53345 KVM: Don't WARN if memory is dirtied without a vCPU when the VM is dying

In the Linux kernel, the following vulnerability has been resolved: KVM: Don't WARN if memory is dirtied without a vCPU when the VM is dying When marking a page dirty, complain about not having a running/loaded vCPU if and only if the VM is still alive, i.e. its refcount is non-zero. This will...

5.8AI score
SaveExploits0References8
Rows per page
Query Builder