CVE-2026-64019

Technical details are not publicly available in the provided documents; monitor for updates.

CVE-2026-64019

In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix dma mapping leak on data setup error We're leaking the initial DMA mapping during iteration if we fail to allocate the tracking descriptor for both PRP and SGL. Unmap the iterator directly; we can't use the existing...

CVE-2026-64019 nvme-pci: fix dma mapping leak on data setup error

In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix dma mapping leak on data setup error We're leaking the initial DMA mapping during iteration if we fail to allocate the tracking descriptor for both PRP and SGL. Unmap the iterator directly; we can't use the existing...

CVE-2026-64019 nvme-pci: fix dma mapping leak on data setup error

In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix dma mapping leak on data setup error We're leaking the initial DMA mapping during iteration if we fail to allocate the tracking descriptor for both PRP and SGL. Unmap the iterator directly; we can't use the existing...

EUVD-2026-45592

In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix dma mapping leak on data setup error We're leaking the initial DMA mapping during iteration if we fail to allocate the tracking descriptor for both PRP and SGL. Unmap the iterator directly; we can't use the existing...

EUVD-2026-45725

In the Linux kernel, the following vulnerability has been resolved: memfd: deny writeable mappings when implying SEALWRITE When SEALEXEC is added, SEALWRITE is implied to make W^X. But the implied seal is set after the check that makes sure the memfd can not have any writable mappings. This means...

CVE-2026-63952 memfd: deny writeable mappings when implying SEAL_WRITE

In the Linux kernel, the following vulnerability has been resolved: memfd: deny writeable mappings when implying SEALWRITE When SEALEXEC is added, SEALWRITE is implied to make W^X. But the implied seal is set after the check that makes sure the memfd can not have any writable mappings. This means...

CVE-2026-63950

Summary: CVE-2026-63950 pertains to the Linux kernel mm/rmap path. The issue arose from not reinitializing nr_pages at the start of each loop in try_to_unmap_one, allowing a value from a previous folio_unmap_pte_batch() to be reused in a later iteration. This could cause corruption of folio refco...

CVE-2026-63950 mm/rmap: initialize nr_pages to 1 at loop start in try_to_unmap_one

In the Linux kernel, the following vulnerability has been resolved: mm/rmap: initialize nrpages to 1 at loop start in trytounmapone Initialize nrpages to 1 at the start of each loop iteration, like folioreferencedone does. Without this, nrpages computed by a previous foliounmapptebatch call can b...

CVE-2026-63916

CVE-2026-63916 affects the Linux kernel HID subsystem for Wacom devices. The vulnerability arises because wacom_hid_set_device_mode() assumed HID_DG_INPUTMODE always resides in the first feature-report field (field[0]). If HID_DG_INPUTMODE is in another field and the first field’s report_count is...

CVE-2026-63916 HID: wacom: Fix OOB write in wacom_hid_set_device_mode()

In the Linux kernel, the following vulnerability has been resolved: HID: wacom: Fix OOB write in wacomhidsetdevicemode wacomhidsetdevicemode currently assumes that the HIDDGINPUTMODE usage is always located in the first field field0 of the feature report. However, a device can specify...

EUVD-2026-45689

In the Linux kernel, the following vulnerability has been resolved: HID: wacom: Fix OOB write in wacomhidsetdevicemode wacomhidsetdevicemode currently assumes that the HIDDGINPUTMODE usage is always located in the first field field0 of the feature report. However, a device can specify...

EUVD-2026-45765

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix lock leak on ENOMEM in AMDGPUGEMOPGETMAPPINGINFO The AMDGPUGEMOPGETMAPPINGINFO branch of amdgpugemopioctl holds three cleanup-tracked resources before calling kvcalloc: the drmgemobject reference from...

CVE-2026-63880 drm/amdgpu: fix lock leak on ENOMEM in AMDGPU_GEM_OP_GET_MAPPING_INFO

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix lock leak on ENOMEM in AMDGPUGEMOPGETMAPPINGINFO The AMDGPUGEMOPGETMAPPINGINFO branch of amdgpugemopioctl holds three cleanup-tracked resources before calling kvcalloc: the drmgemobject reference from...

CVE-2026-63880 drm/amdgpu: fix lock leak on ENOMEM in AMDGPU_GEM_OP_GET_MAPPING_INFO

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix lock leak on ENOMEM in AMDGPUGEMOPGETMAPPINGINFO The AMDGPUGEMOPGETMAPPINGINFO branch of amdgpugemopioctl holds three cleanup-tracked resources before calling kvcalloc: the drmgemobject reference from...

CVE-2026-63880

CVE-2026-63880 affects the Linux kernel AMDGPU driver (drm/amdgpu) in the AMDGPU_GEM_OP_GET_MAPPING_INFO path. A -ENOMEM failure in kvcalloc could skip cleanup and leak three locks (drm_gem_object reference, drm_exec lock on the GEM, and drm_exec lock on the per-process VM root PD), causing a loa...

CVE-2026-63880

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix lock leak on ENOMEM in AMDGPUGEMOPGETMAPPINGINFO The AMDGPUGEMOPGETMAPPINGINFO branch of amdgpugemopioctl holds three cleanup-tracked resources before calling kvcalloc: the drmgemobject reference from...

CVE-2026-63878

The CVE-2026-63878 entry concerns the Linux kernel driver drm/amdgpu, specifically GEM_OP GET_MAPPING_INFO. The issue arises when user-supplied num_entries is used directly to allocate memory via kvcalloc without an upper bound, with num_entries as __u32 and each entry-sized 32 bytes. This can le...

EUVD-2026-45763

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: check numentries in GEMOP GETMAPPINGINFO kvcallocargs-numentries, sizeofvmentries, GFPKERNEL at amdgpugem.c:1050 uses the user-supplied numentries directly without any upper bounds check. Since numentries is a u32 and...

CVE-2026-63878

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: check numentries in GEMOP GETMAPPINGINFO kvcallocargs-numentries, sizeofvmentries, GFPKERNEL at amdgpugem.c:1050 uses the user-supplied numentries directly without any upper bounds check. Since numentries is a u32 and...