CVE-2026-72112

A flaw was found in the Linux kernel's iouring/bpf-ops component. This vulnerability allows a local attacker with specific capabilities CAPBPF and CAPPERFMON to re-register an already-bound operation, leading to a use-after-free of freed executable memory. This could result in arbitrary code...

CVE-2026-72111

A flaw was found in the Linux kernel's BPF verifier. When processing a context load of an LSM hook return value, the markregs32range function incorrectly intersects new register bounds with stale ones, rather than replacing them. This can lead to a mismatch between the verifier's understanding of...

CVE-2026-72110

A flaw was found in the Linux kernel's BPF/fork component. A local user, by initiating a fork operation from a process within a task storage map, can trigger a condition where the bpfstorage is not properly initialized. This can lead to a Use-After-Free UAF vulnerability, which occurs when the...

CVE-2026-72109

A flaw was found in the Linux kernel's sparx5 network driver. An improper cleanup during initialization failure can leave a switchdev blocking notifier registered. This issue could lead to resource exhaustion or system instability, potentially resulting in a Denial of Service DoS condition...

CVE-2026-72108

A flaw was found in the Linux kernel's device-mapper dm thin metadata component. When operations involving metadata snapshots, such as reserving or releasing a snapshot, encounter a commit failure, the system can write an inconsistent 'heldroot' to disk. This can lead to metadata corruption withi...

CVE-2026-72107

A flaw was found in the Linux kernel's device-mapper dm-era component. This vulnerability arises from an incorrect calculation of writeset blocks, which can lead to an out-of-bounds memory access. An attacker could potentially exploit this to cause a denial of service or other undefined behavior...

CVE-2026-72106

A flaw was found in the dm-ioctl component of the Linux kernel. This vulnerability, a buffer overflow, occurs in the listversiongetinfo function when the code attempts to write more data than the allocated buffer size. A local attacker could potentially exploit this to cause a denial of service o...

CVE-2026-72105

A flaw was found in the Linux kernel's device mapper logging dm-log component. On 32-bit systems, an error in calculating the bitsetsize can cause this variable to wrap around to zero. This incorrect calculation leads to a failure in memory allocation, which can result in a Denial of Service DoS...

CVE-2026-72103

A flaw was found in the Linux kernel's device-mapper dm component. A refactoring error caused the caller's thread keyring, which can contain sensitive data like LUKS volume keys, to persist in memory longer than intended. This issue allows a local attacker with administrative privileges to recove...

CVE-2026-72102

A flaw was found in the Linux kernel's device mapper DM subsystem. During certain resume operations, the kernel might attempt to free a memory table that has already been released. This error, known as a double-free vulnerability, can lead to memory corruption. A successful exploit could result i...

CVE-2026-72101

A flaw was found in dm-integrity, a component of the Linux kernel. This vulnerability occurs when the hash size is less than the device's tuple size, and dm-integrity fails to properly zero out the remaining memory space. This oversight can lead to the leaking of uninitialized kernel memory,...

CVE-2026-72098

A flaw was found in the dm-verity component of the Linux kernel. A buffer overflow occurs during Forward Error Correction FEC calculation, allowing an attacker to write past the end of an allocated buffer. This out-of-bounds write can corrupt the syndrome buffer, potentially leading to system...

CVE-2026-72097

A flaw was found in the Linux kernel's dm-verity component. A possible NULL pointer dereference can occur in the dmverityloadpinisbdevtrusted function if a device lacks a table. This vulnerability could allow a local attacker to cause a system crash, leading to a Denial of Service DoS...

CVE-2026-72096

A flaw was found in the Linux kernel's dm-verity component. The 'corruptederrs' counter, which tracks errors in corrupted blocks, was not atomic. This vulnerability could allow a race condition to occur, potentially causing the system to skip auditing when the maximum number of corrupted errors i...

CVE-2026-72095

A flaw was found in the Linux kernel's dma-fence component. The dmafencededuparray function incorrectly handles zero-count input, leading to a memory corruption vulnerability. A local attacker could potentially exploit this by triggering specific conditions in the amdgpuuserqwait functions, which...

CVE-2026-72094

A flaw was found in the Linux kernel's dma-fence subsystem. This vulnerability arises from a timing issue on weakly ordered platforms, where memory operations related to fence signaling and pointer nullification can occur out of order. This can lead to a NULL pointer dereference, potentially...

CVE-2026-72093

A flaw was found in the Linux kernel, specifically within the amdxdna graphics driver. This vulnerability is a use-after-free error, where a memory object is incorrectly freed twice when certain memory allocation operations fail. This leads to memory corruption. A local attacker could potentially...

CVE-2026-72091

A flaw was found in the Linux kernel's AMD XDNA accelerator driver. An attacker with local access to the accelerator node can trigger a null pointer dereference by submitting a command with an invalid command buffer object. This can lead to a kernel crash, resulting in a denial of service DoS for...

CVE-2026-72090

A flaw was found in the Linux kernel's amdxdna graphics acceleration driver. A local user could exploit an incorrect client handling issue within the amdxdnadrmsyncboioctl function. When performing a SYNCDIRECTFROMDEVICE operation, the amdxdnahwctxsyncdebugbo function is called with an incorrect...

CVE-2026-72089

A flaw was found in the Linux kernel's Intel Versatile Processing Unit IVPU accelerator driver. An attacker could exploit a vulnerability in how the driver handles firmware logs with incorrect size information. This could lead to an out-of-bounds read, potentially disclosing sensitive information...