29589 matches found
CVE-2026-64110
In the Linux kernel, the following vulnerability has been resolved: igc: fix potential skb leak in igcfpexmitsmdframe When igcfpeinittxdescriptor fails, no one takes care of an allocated skb, leaking it. 1 Use devkfreeskbany on failure. Tested on an I226 adapter with the following command, while...
EUVD-2026-45795
In the Linux kernel, the following vulnerability has been resolved: igc: fix potential skb leak in igcfpexmitsmdframe When igcfpeinittxdescriptor fails, no one takes care of an allocated skb, leaking it. 1 Use devkfreeskbany on failure. Tested on an I226 adapter with the following command, while...
CVE-2026-64110 igc: fix potential skb leak in igc_fpe_xmit_smd_frame()
In the Linux kernel, the following vulnerability has been resolved: igc: fix potential skb leak in igcfpexmitsmdframe When igcfpeinittxdescriptor fails, no one takes care of an allocated skb, leaking it. 1 Use devkfreeskbany on failure. Tested on an I226 adapter with the following command, while...
CVE-2026-64110 igc: fix potential skb leak in igc_fpe_xmit_smd_frame()
In the Linux kernel, the following vulnerability has been resolved: igc: fix potential skb leak in igcfpexmitsmdframe When igcfpeinittxdescriptor fails, no one takes care of an allocated skb, leaking it. 1 Use devkfreeskbany on failure. Tested on an I226 adapter with the following command, while...
CVE-2026-64105
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Free privateirqs when init fails after allocation Companion to commit 250f25367b58 "KVM: arm64: Tear down vGIC on failed vCPU creation", which added the missing kvmvgicvcpudestroy call to the kvmsharehyp failure...
EUVD-2026-45790
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Free privateirqs when init fails after allocation Companion to commit 250f25367b58 "KVM: arm64: Tear down vGIC on failed vCPU creation", which added the missing kvmvgicvcpudestroy call to the kvmsharehyp failure...
CVE-2026-64105
The CVE concerns the Linux kernel KVM for arm64 vgic. A failure during vCPU creation could leak private IRQs if allocation happened before a redistributor iodev registration failure. The fix adds a call to kvm_vgic_vcpu_destroy() on the kvm_vgic_vcpu_init() failure path, ensuring that private IRQ...
CVE-2026-64105
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Free privateirqs when init fails after allocation Companion to commit 250f25367b58 "KVM: arm64: Tear down vGIC on failed vCPU creation", which added the missing kvmvgicvcpudestroy call to the kvmsharehyp failure...
CVE-2026-64105 KVM: arm64: vgic: Free private_irqs when init fails after allocation
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Free privateirqs when init fails after allocation Companion to commit 250f25367b58 "KVM: arm64: Tear down vGIC on failed vCPU creation", which added the missing kvmvgicvcpudestroy call to the kvmsharehyp failure...
CVE-2026-64105 KVM: arm64: vgic: Free private_irqs when init fails after allocation
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Free privateirqs when init fails after allocation Companion to commit 250f25367b58 "KVM: arm64: Tear down vGIC on failed vCPU creation", which added the missing kvmvgicvcpudestroy call to the kvmsharehyp failure...
CVE-2026-64104
CVE-2026-64104 (Linux kernel) affects virt: sev-guest where set_memory_encrypted()/set_memory_decrypted() can fail leaving pages in an unknown state, potentially unencrypted and not safely returnable to the buddy allocator. The provided documentation notes that to avoid this, the pages should not...
CVE-2026-64104 virt: sev-guest: Explicitly leak pages in unknown state
In the Linux kernel, the following vulnerability has been resolved: virt: sev-guest: Explicitly leak pages in unknown state When setmemoryencrypted,decrypted fail, the user cannot know at which point the function failed, meaning that the pages are left in an unknown state from the point of view o...
EUVD-2026-45783
In the Linux kernel, the following vulnerability has been resolved: drm/virtio: use uninterruptible resv lock for plane updates virtiogpucursorplaneupdate and virtiogpuresourceflush lock the framebuffer BO's dmaresv via virtiogpuarraylockresv and ignore its return value. The function can fail wit...
CVE-2026-64098
In the Linux kernel, the following vulnerability has been resolved: drm/virtio: use uninterruptible resv lock for plane updates virtiogpucursorplaneupdate and virtiogpuresourceflush lock the framebuffer BO's dmaresv via virtiogpuarraylockresv and ignore its return value. The function can fail wit...
CVE-2026-64082
In the Linux kernel, the following vulnerability has been resolved: riscv: Fix register corruption from uninitialized cregs on error compatriscvgprset calls cregstoregs unconditionally, even when userregsetcopyin fails. Since cregs is an uninitialized stack variable, a copyin failure causes...
CVE-2026-64082
The CVE-2026-64082 issue affects the Linux kernel on riscv where uninitialized cregs data could be written to a task’s pt_regs during error paths. Specifically, compat_riscv_gpr_set() and compat_restore_sigcontext() call cregs_to_regs() unconditionally, even when user_regset_copyin() or __copy_fr...
CVE-2026-64082 riscv: Fix register corruption from uninitialized cregs on error
In the Linux kernel, the following vulnerability has been resolved: riscv: Fix register corruption from uninitialized cregs on error compatriscvgprset calls cregstoregs unconditionally, even when userregsetcopyin fails. Since cregs is an uninitialized stack variable, a copyin failure causes...
CVE-2026-64072 nvme: fix bio leak on mapping failure
In the Linux kernel, the following vulnerability has been resolved: nvme: fix bio leak on mapping failure The local bio is always NULL, so we'd leak the bio if the integrity mapping failed. Just get it directly from the request...
CVE-2026-64072
In the Linux kernel, the following vulnerability has been resolved: nvme: fix bio leak on mapping failure The local bio is always NULL, so we'd leak the bio if the integrity mapping failed. Just get it directly from the request...
EUVD-2026-45645
In the Linux kernel, the following vulnerability has been resolved: nvme: fix bio leak on mapping failure The local bio is always NULL, so we'd leak the bio if the integrity mapping failed. Just get it directly from the request...