kernel: xen/privcmd: fix double free via VMA splitting

A flaw was found in the Linux kernel's xen/privcmd module. A local user could exploit this by performing a partial unmapping of a privcmd memory region. This action causes a Virtual Memory Area VMA to split, leading to duplicated internal memory pointers. As a result, the same memory can be freed...

kernel: xen/privcmd: fix double free via VMA splitting

A flaw was found in the Linux kernel's xen/privcmd module. A local user could exploit this by performing a partial unmapping of a privcmd memory region. This action causes a Virtual Memory Area VMA to split, leading to duplicated internal memory pointers. As a result, the same memory can be freed...

kernel: xen/privcmd: fix double free via VMA splitting

A flaw was found in the Linux kernel's xen/privcmd module. A local user could exploit this by performing a partial unmapping of a privcmd memory region. This action causes a Virtual Memory Area VMA to split, leading to duplicated internal memory pointers. As a result, the same memory can be freed...

kernel: xen/privcmd: fix double free via VMA splitting

A flaw was found in the Linux kernel's xen/privcmd module. A local user could exploit this by performing a partial unmapping of a privcmd memory region. This action causes a Virtual Memory Area VMA to split, leading to duplicated internal memory pointers. As a result, the same memory can be freed...

Linux Distros Unpatched Vulnerability : CVE-2026-64254

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - NTB: epf: Avoid pciiounmap with offset when PEERSPAD and CONFIG share BAR When BARPEERSPAD and BARCONFIG share one PCI BAR, the module teardown path ends up...

SUSE CVE-2026-64254

In the Linux kernel, the following vulnerability has been resolved: NTB: epf: Avoid pciiounmap with offset when PEERSPAD and CONFIG share BAR When BARPEERSPAD and BARCONFIG share one PCI BAR, the module teardown path ends up calling pciiounmap on the same iomem with some offset, which is...

CVE-2026-64254

The CVE-2026-64254 issue concerns the Linux kernel NTB epf driver where, during teardown, pci_iounmap() could be invoked on the same iomem with an offset when BAR_PEER_SPAD and BAR_CONFIG share a PCI BAR. This caused a kernel warning such as vunmap() on a nonexistent VM area. The documented fix e...

PT-2026-64369

In the Linux kernel, the following vulnerability has been resolved: NTB: epf: Avoid pci iounmap with offset when PEER SPAD and CONFIG share BAR When BAR PEER SPAD and BAR CONFIG share one PCI BAR, the module teardown path ends up calling pci iounmap on the same iomem with some offset, which is...

CVE-2026-63950

A flaw was found in the Linux kernel's memory management. A local user can trigger an issue where an incorrectly initialized page counter during memory unmapping operations leads to corruption of internal memory structures. This can cause the kernel to crash, resulting in a Denial of Service DoS...

SUSE CVE-2026-53373

In the Linux kernel, the following vulnerability has been resolved: mm/vma: do not try to unmap a VMA if mmapprepare invoked from mmap The mmapprepare hook functionality includes the ability to invoke mmapprepare from the mmap hook of existing 'stacked' drivers, that is ones which are capable of...

CVE-2026-64131

A flaw was found in the Linux kernel's memory management subsystem. The unmapping process for device-private and exclusive memory pages incorrectly checks if a virtual memory area VMA is anonymous. This can lead to spurious warnings during process teardown when a folio is part of a private...

CVE-2026-64112

A flaw was found in the Linux kernel's Rados Block Device RBD module. A race condition exists in the lockdwork draining mechanism during the unmapping of an image. This allows the lockdwork to be re-queued after it is expected to be finalized, potentially leading to rbdacquirelock executing on...

Linux Distros Unpatched Vulnerability : CVE-2026-53373

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - In the Linux kernel, the following vulnerability has been resolved: mm/vma: do not try to unmap a VMA if mmapprepare invoked from mmap The mmapprepare hook...

CVE-2026-64131

CVE-2026-64131 : In the Linux kernel, a misinterpretation in the unmap path could cause spurious warnings and device-private/exclusive folios to be migrated incorrectly. The code tested folio_test_anon() for device-private support but then checked vma_is_anonymous() elsewhere, which is not a guar...

CVE-2026-64131 mm/memory: fix spurious warning when unmapping device-private/exclusive pages

In the Linux kernel, the following vulnerability has been resolved: mm/memory: fix spurious warning when unmapping device-private/exclusive pages Device private and exclusive entries are only supported for anonymous folios. This condition is tested in migratedevicepages and makedeviceexclusive...

CVE-2026-64131 mm/memory: fix spurious warning when unmapping device-private/exclusive pages

In the Linux kernel, the following vulnerability has been resolved: mm/memory: fix spurious warning when unmapping device-private/exclusive pages Device private and exclusive entries are only supported for anonymous folios. This condition is tested in migratedevicepages and makedeviceexclusive...

EUVD-2026-45797

In the Linux kernel, the following vulnerability has been resolved: rbd: eliminate a race in lockdwork draining on unmap Given how rbdlockaddrequest and rbdimgexclusivelock are written, lockdwork may be requeued more than it's actually needed: for example in case a new I/O request comes in while ...

CVE-2026-64020

In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix dmavecs leak on p2p memory We don't unmap P2P memory, so we don't need to track it. The dmavec allocation was getting leaked on the completion...

EUVD-2026-45593

In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix dmavecs leak on p2p memory We don't unmap P2P memory, so we don't need to track it. The dmavec allocation was getting leaked on the completion...

CVE-2026-53373

The CVE-2026-53373 issue is in the Linux kernel’s mm/vma path: in certain stacked driver scenarios, mmap_prepare() invoked from the mmap() hook may expose a not-fully-established VMA to the caller, risking unsafe unmapping as the VMA is detached. The fix propagates the context of the mmap action ...