Lucene search
K

12694 matches found

NVD
NVD
added 2026/04/24 3:16 p.m.2 views

CVE-2026-31593

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Reject attempts to sync VMSA of an already-launched/encrypted vCPU Reject synchronizing vCPU state to its associated VMSA if the vCPU has already been launched, i.e. if the VMSA has already been encrypted. On a host wit...

5.5CVSS0.00015EPSS
Exploits0References5
NVD
NVD
added 2026/04/24 3:16 p.m.1 views

CVE-2026-31591

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Lock all vCPUs when synchronzing VMSAs for SNP launch finish Lock all vCPUs when synchronizing and encrypting VMSAs for SNP guests, as allowing userspace to manipulate and/or run a vCPU while its state is being...

5.5CVSS0.00015EPSS
Exploits0References4
NVD
NVD
added 2026/04/24 3:16 p.m.2 views

CVE-2026-31588

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Use scratch field in MMIO fragment to hold small write values When exiting to userspace to service an emulated MMIO write, copy the to-be-written value to a scratch field in the MMIO fragment if the size of the data...

8.8CVSS0.00015EPSS
Exploits0References9
NVD
NVD
added 2026/04/24 3:16 p.m.1 views

CVE-2026-31561

In the Linux kernel, the following vulnerability has been resolved: x86/cpu: Remove X86CR4FRED from the CR4 pinned bits mask Commit in Fixes added the FRED CR4 bit to the CR4 pinned bits mask so that whenever something else modifies CR4, that bit remains set. Which in itself is a perfectly fine...

5.5CVSS0.00015EPSS
Exploits0References4
OSV
OSV
added 2026/04/24 3:16 p.m.0 views

DEBIAN-CVE-2026-31553

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Fix the descriptor address in kvmatswapdesc Using "u64 user hva + offset" to get the virtual addresses of S1/S2 descriptors looks really wrong, if offset is not zero. What we want to get for swapping is hva + offset,...

8.8CVSS5.3AI score0.00017EPSS
Exploits0References1
UbuntuCve
UbuntuCve
added 2026/04/24 3:16 p.m.1 views

CVE-2026-31564

In the Linux kernel, the following vulnerability has been resolved: LoongArch: KVM: Fix base address calculation in kvmeiointcregsaccess In function kvmeiointcregsaccess, the register base address is caculated from array base address plus offset, the offset is absolute value from the base address...

5.5CVSS5.4AI score0.00017EPSS
Exploits0References4
UbuntuCve
UbuntuCve
added 2026/04/24 3:16 p.m.3 views

CVE-2026-31553

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Fix the descriptor address in kvmatswapdesc Using "u64 user hva + offset" to get the virtual addresses of S1/S2 descriptors looks really wrong, if offset is not zero. What we want to get for swapping is hva + offset,...

8.8CVSS5.4AI score0.00017EPSS
Exploits0References4
UbuntuCve
UbuntuCve
added 2026/04/24 3:16 p.m.0 views

CVE-2026-31558

In the Linux kernel, the following vulnerability has been resolved: LoongArch: KVM: Make kvmgetvcpubycpuid more robust kvmgetvcpubycpuid takes a cpuid parameter whose type is int, so cpuid can be negative. Let kvmgetvcpubycpuid return NULL for this case so as to make it more robust. This fix an...

8.8CVSS5.4AI score0.00015EPSS
Exploits0References6
UbuntuCve
UbuntuCve
added 2026/04/24 3:16 p.m.3 views

CVE-2026-31561

In the Linux kernel, the following vulnerability has been resolved: x86/cpu: Remove X86CR4FRED from the CR4 pinned bits mask Commit in Fixes added the FRED CR4 bit to the CR4 pinned bits mask so that whenever something else modifies CR4, that bit remains set. Which in itself is a perfectly fine...

5.5CVSS5.4AI score0.00015EPSS
Exploits0References6
Cvelist
Cvelist
added 2026/04/24 2:42 p.m.24 views

CVE-2026-31593 KVM: SEV: Reject attempts to sync VMSA of an already-launched/encrypted vCPU

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Reject attempts to sync VMSA of an already-launched/encrypted vCPU Reject synchronizing vCPU state to its associated VMSA if the vCPU has already been launched, i.e. if the VMSA has already been encrypted. On a host wit...

0.00015EPSS
Exploits0References5
EUVD
EUVD
added 2026/04/24 2:42 p.m.3 views

EUVD-2026-25486

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Reject attempts to sync VMSA of an already-launched/encrypted vCPU Reject synchronizing vCPU state to its associated VMSA if the vCPU has already been launched, i.e. if the VMSA has already been encrypted. On a host wit...

5.4AI score0.00015EPSS
Exploits0References4
CVE
CVE
added 2026/04/24 2:42 p.m.10 views

CVE-2026-31592

CVE-2026-31592 affects the Linux kernel KVM subsystem. The vulnerability arises when sev_mem_enc_register_region() is not protected by kvm->lock before sev_guest() is checked, risking state corruption if KVM_INIT{2} fails and an uninitialized sev->regions_list is touched, potentially causin...

5.5CVSS5.4AI score0.00015EPSS
Exploits0References4Affected Software1
Cvelist
Cvelist
added 2026/04/24 2:42 p.m.26 views

CVE-2026-31591 KVM: SEV: Lock all vCPUs when synchronzing VMSAs for SNP launch finish

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Lock all vCPUs when synchronzing VMSAs for SNP launch finish Lock all vCPUs when synchronizing and encrypting VMSAs for SNP guests, as allowing userspace to manipulate and/or run a vCPU while its state is being...

0.00015EPSS
Exploits0References4
ATTACKERKB
ATTACKERKB
added 2026/04/24 2:42 p.m.0 views

CVE-2026-31592

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Protect all of sevmemencregisterregion with kvm-lock Take and hold kvm-lock for before checking sevguest in sevmemencregisterregion, as sevguest isn't stable unless kvm-lock is held or KVM can guarantee KVMSEVINIT2 has...

5.2AI score0.00015EPSS
Exploits0References5Affected Software1
EUVD
EUVD
added 2026/04/24 2:42 p.m.2 views

EUVD-2026-25485

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Protect all of sevmemencregisterregion with kvm-lock Take and hold kvm-lock for before checking sevguest in sevmemencregisterregion, as sevguest isn't stable unless kvm-lock is held or KVM can guarantee KVMSEVINIT2 has...

5.4AI score0.00015EPSS
Exploits0References3
EUVD
EUVD
added 2026/04/24 2:42 p.m.0 views

EUVD-2026-25484

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Lock all vCPUs when synchronzing VMSAs for SNP launch finish Lock all vCPUs when synchronizing and encrypting VMSAs for SNP guests, as allowing userspace to manipulate and/or run a vCPU while its state is being...

5.4AI score0.00015EPSS
Exploits0References3
Cvelist
Cvelist
added 2026/04/24 2:42 p.m.30 views

CVE-2026-31588 KVM: x86: Use scratch field in MMIO fragment to hold small write values

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Use scratch field in MMIO fragment to hold small write values When exiting to userspace to service an emulated MMIO write, copy the to-be-written value to a scratch field in the MMIO fragment if the size of the data...

8.8CVSS0.00015EPSS
Exploits0References9
Debian CVE
Debian CVE
added 2026/04/24 2:42 p.m.2 views

CVE-2026-31588

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Use scratch field in MMIO fragment to hold small write values When exiting to userspace to service an emulated MMIO write, copy the to-be-written value to a scratch field in the MMIO fragment if the size of the data...

8.8CVSS5.4AI score0.00015EPSS
Exploits0
ATTACKERKB
ATTACKERKB
added 2026/04/24 2:42 p.m.3 views

CVE-2026-31588

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Use scratch field in MMIO fragment to hold small write values When exiting to userspace to service an emulated MMIO write, copy the to-be-written value to a scratch field in the MMIO fragment if the size of the data...

8.8CVSS5.3AI score0.00015EPSS
Exploits0References7Affected Software1
Debian CVE
Debian CVE
added 2026/04/24 2:35 p.m.1 views

CVE-2026-31569

In the Linux kernel, the following vulnerability has been resolved: LoongArch: KVM: Handle the case that EIOINTC's coremap is empty EIOINTC's coremap in eiointcupdateswcoremap can be empty, currently we get a cpuid with -1 in this case, but we actually need 0 because it's similar as the case that...

7.3CVSS5.3AI score0.00015EPSS
Exploits0
Rows per page
Query Builder