Lucene search
+L

321 matches found

RedhatCVE
RedhatCVE
added yesterday3 views

CVE-2026-63940

A flaw was found in the Linux kernel's Kernel-based Virtual Machine KVM Secure Encrypted Virtualization SEV module. This vulnerability occurs because the system does not properly handle Port I/O requests with a length of zero. An attacker, potentially from a guest virtual machine, could exploit...

9.3CVSS5.3AI score0.00182EPSS
Exploits0References4
RedhatCVE
RedhatCVE
added yesterday2 views

CVE-2026-63938

A flaw was found in the Linux kernel's Kernel-based Virtual Machine KVM Secure Encrypted Virtualization SEV feature. When processing Page State Change PSC requests, the system does not properly validate the PSC buffer against the effective size of the scratch area. This can occur if a guest...

9.3CVSS5.5AI score0.00182EPSS
Exploits0References4
RedhatCVE
RedhatCVE
added yesterday2 views

CVE-2026-63939

A flaw was found in the Linux kernel's Kernel-based Virtual Machine KVM with Secure Encrypted Virtualization SEV support. This vulnerability arises from an incorrect calculation of the maximum length for the in-Guest-Host Communication Block GHCB scratch area. When processing Page State Change PS...

9.3CVSS5.9AI score0.00197EPSS
Exploits0References4
RedhatCVE
RedhatCVE
added yesterday4 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.5AI score0.00163EPSS
Exploits0References4
NVD
NVD
added 3 days ago7 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.00182EPSS
Exploits0References4
NVD
NVD
added 3 days ago8 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.00197EPSS
Exploits0References4
EUVD
EUVD
added 3 days ago8 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.4AI score0.00182EPSS
Exploits0References4
CVE
CVE
added 3 days ago12 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.7AI score0.00197EPSS
Exploits0References4
CVE
CVE
added 3 days ago9 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.4AI score0.00182EPSS
Exploits0References4
Cvelist
Cvelist
added 3 days ago31 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.00197EPSS
Exploits0References4
OSV
OSV
added 3 days ago5 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 score0.00163EPSS
Exploits0References7
CVE
CVE
added 3 days ago10 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.5AI score0.00163EPSS
Exploits0References4
Positive Technologies
Positive Technologies
added 3 days ago13 views

PT-2026-61256

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

5.7AI score0.00197EPSS
Exploits0References5
Positive Technologies
Positive Technologies
added 3 days ago11 views

PT-2026-61255

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

5.3AI score0.00182EPSS
Exploits0References5
RedhatCVE
RedhatCVE
added 2026/07/05 3:4 p.m.7 views

CVE-2026-53360

A flaw was found in the Linux kernel's KVM Kernel-based Virtual Machine subsystem, specifically within the SEV Secure Encrypted Virtualization feature. A malicious guest operating system utilizing SEV-SNP Secure Nested Paging can exploit an out-of-bounds write vulnerability due to improper...

8.8CVSS6.9AI score0.00183EPSS
Exploits0References4
UbuntuCve
UbuntuCve
added 2026/07/04 12:17 p.m.7 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...

6.7AI score0.00183EPSS
Exploits0References6
OSV
OSV
added 2026/07/04 12:17 p.m.6 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.6AI score0.00183EPSS
Exploits0References10
Cvelist
Cvelist
added 2026/07/04 11:53 a.m.46 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.00183EPSS
Exploits0References4
Debian CVE
Debian CVE
added 2026/07/04 11:53 a.m.7 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.8CVSS6AI score0.00183EPSS
Exploits0
OSV
OSV
added 2026/07/01 1:32 p.m.4 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 score0.00156EPSS
Exploits0References8
Rows per page
Query Builder