17131 matches found
SUSE CVE-2026-64479
In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: Fix uninitialised heap leak in sndseqeventdup sndseqeventdup copies an incoming event into a pool cell and, in the UMP-enabled build, clears the trailing cell-ump.raw.extra word that the memcpy did not cover. The guard...
CVE-2026-64360
In the Linux kernel, the following vulnerability has been resolved: hfs/hfsplus: zero-initialize buffer in hfsbnoderead hfsbnoderead can return early without writing to the output buffer when isbnodeoffsetvalid fails or when checkandcorrectrequested length corrects the length to zero. Callers suc...
CVE-2026-64306
In the Linux kernel, the following vulnerability has been resolved: crypto: drbg - Fix returning success on failure in CTRDRBG drbgctrgenerate sometimes returns success when it fails, leaving the output buffer uninitialized. Fix it...
UBUNTU-CVE-2026-64306
In the Linux kernel, the following vulnerability has been resolved: crypto: drbg - Fix returning success on failure in CTRDRBG drbgctrgenerate sometimes returns success when it fails, leaving the output buffer uninitialized. Fix it...
CVE-2026-64500
In the Linux kernel, the following vulnerability has been resolved: iio: adc: lpc32xx: Initialize completion before requesting IRQ In the report from Jaeyoung Chung: "lpc32xxadcprobe in drivers/iio/adc/lpc32xxadc.c registers its interrupt handler with devmrequestirq before it initializes...
UBUNTU-CVE-2026-64360
In the Linux kernel, the following vulnerability has been resolved: hfs/hfsplus: zero-initialize buffer in hfsbnoderead hfsbnoderead can return early without writing to the output buffer when isbnodeoffsetvalid fails or when checkandcorrectrequested length corrects the length to zero. Callers suc...
UBUNTU-CVE-2026-64309
In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Do not initialize SNP for ioctlSNPCOMMIT Sashiko notes: if SEV initialization fails and KVM is actively running normal VMs, could a userspace process trigger this code path via /dev/sev ioctls e.g., SEVPDHGEN and ze...
UBUNTU-CVE-2026-64413
In the Linux kernel, the following vulnerability has been resolved: netfilter: ebtables: zero chainstack array sashiko reports: looking at ebtables table translation, could a sparse cpupossiblemask lead to an uninitialized pointer free? If cpupossiblemask is sparse for example, CPU 0 and CPU 2 ar...
CVE-2026-64479
In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: Fix uninitialised heap leak in sndseqeventdup sndseqeventdup copies an incoming event into a pool cell and, in the UMP-enabled build, clears the trailing cell-ump.raw.extra word that the memcpy did not cover. The guard...
CVE-2026-64413 netfilter: ebtables: zero chainstack array
In the Linux kernel, the following vulnerability has been resolved: netfilter: ebtables: zero chainstack array sashiko reports: looking at ebtables table translation, could a sparse cpupossiblemask lead to an uninitialized pointer free? If cpupossiblemask is sparse for example, CPU 0 and CPU 2 ar...
CVE-2026-64413
CVE-2026-64413 relates to the Linux kernel netfilter/ebtables path, specifically the zero chainstack array issue. The advisory describes that if cpu_possible_mask is sparse (e.g., CPU 0 and CPU 2 possible, CPU 1 not), the allocation loop can skip an entry and, if vmalloc_node() fails later, the c...
CVE-2026-64360
CVE-2026-64360 affecting the Linux kernel’s HFS/HFS+ code (hfs_bnode_read) was fixed by zero-initializing the output buffer at the start of hfs_bnode_read to ensure deterministic zero values across all paths. The bug allowed early returns when is_bnode_offset_valid() failed or when check_and_corr...
EUVD-2026-48904
In the Linux kernel, the following vulnerability has been resolved: hfs/hfsplus: zero-initialize buffer in hfsbnoderead hfsbnoderead can return early without writing to the output buffer when isbnodeoffsetvalid fails or when checkandcorrectrequested length corrects the length to zero. Callers suc...
CVE-2026-64360 hfs/hfsplus: zero-initialize buffer in hfs_bnode_read
In the Linux kernel, the following vulnerability has been resolved: hfs/hfsplus: zero-initialize buffer in hfsbnoderead hfsbnoderead can return early without writing to the output buffer when isbnodeoffsetvalid fails or when checkandcorrectrequested length corrects the length to zero. Callers suc...
EUVD-2026-49021
In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Do not initialize SNP for ioctlSNPCOMMIT Sashiko notes: if SEV initialization fails and KVM is actively running normal VMs, could a userspace process trigger this code path via /dev/sev ioctls e.g., SEVPDHGEN and ze...
CVE-2026-64309 crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT)
In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Do not initialize SNP for ioctlSNPCOMMIT Sashiko notes: if SEV initialization fails and KVM is actively running normal VMs, could a userspace process trigger this code path via /dev/sev ioctls e.g., SEVPDHGEN and ze...
CVE-2026-64309
The CVE-2026-64309 entry concerns the Linux kernel crypto/ccp path where SNP_COMMIT initialization was inappropriately performed. The remediation implemented is to skip initializing SNP_COMMIT when the SEV-SNP firmware is uninitialized, i.e., the SNP_COMMIT command is allowed in UNINIT but previo...
CVE-2026-64306
The CVE-2026-64306 issue affects the Linux kernel crypto DRBG (CTR_DRBG). The root cause is in drbg_ctr_generate(), which could return success after a failure, leaving the output buffer uninitialized. This vulnerability is addressed by the kernel fix that prevents returning success on failure and...
EUVD-2026-49018
In the Linux kernel, the following vulnerability has been resolved: crypto: drbg - Fix returning success on failure in CTRDRBG drbgctrgenerate sometimes returns success when it fails, leaving the output buffer uninitialized. Fix it...
PT-2026-64527
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the CTR DRBG component where the drbg ctr generate function may incorrectly return a success status despite failing, which results in the output buffer remaining...