2781 matches found
CVE-2026-80960
A flaw was found in the Linux kernel's dm-pcache component. A local attacker with CAPSYSADMIN capabilities can exploit this vulnerability by supplying a specially crafted cache device. The segnum value, which dictates the size of cache segments, is not adequately validated against the actual devi...
CVE-2026-80963
A flaw was found in the Linux kernel's dm-stats module. This vulnerability occurs when the allocation of per-CPU data fails, which can lead to a null pointer dereference during the subsequent cleanup operation. This issue can cause the system to crash, resulting in a Denial of Service DoS...
CVE-2026-80956
A flaw was found in the Linux kernel's dm-pcache component. A crafted image can cause the getcachesegment function to return an uninitialized cache segment. This uninitialized segment, containing a null data pointer, is then used by cacheksetclose without a proper null check. This can lead to a...
CVE-2026-80959
A flaw was found in the Linux kernel's device-mapper persistent cache dm-pcache component. A local attacker with administrative privileges CAPSYSADMIN could provide a specially crafted cache device, leading to an out-of-bounds read. This vulnerability allows reading past the intended segment data...
CVE-2026-80962
A flaw was found in the Linux kernel's dm-pcache component. A local attacker with administrative privileges CAPSYSADMIN could manipulate on-disk cache metadata to provide invalid geometry fields. This manipulation could lead to an out-of-bounds read and write, potentially causing memory corruptio...
CVE-2026-89576
A flaw was found in the Linux kernel's device-mapper era dm-era component. When a snapshot operation fails, a block of metadata is allocated but not properly freed. This leads to a permanent leak of system resources with each failed attempt. Over time, this resource exhaustion can result in a...
CVE-2026-89575
A flaw was found in the Linux kernel's device mapper dm-raid1 component. This vulnerability occurs in the buildconstructorstring function, where insufficient space is reserved for a NUL-terminator when formatting a string with sprintf. This oversight can lead to a buffer overflow, potentially...
CVE-2026-89578
A flaw was found in the Linux kernel's device mapper I/O dm-io component. When handling DMIOBIO requests, incorrect sector-based accounting for misaligned direct I/O buffers could lead to an infinite loop. This issue can cause I/O operations to hang indefinitely, resulting in a denial of service...
CVE-2026-89573
A flaw was found in the Linux kernel's device mapper dm array component. A local attacker could exploit this vulnerability by providing specially crafted metadata. This crafted metadata causes the system to misinterpret the size of data blocks, leading to an out-of-bounds read. This memory...
CVE-2026-89574
A flaw was found in the Linux kernel's device mapper dm array component. Insufficient validation of array block headers during read operations allows a local attacker to craft a malicious on-disk nrentries value. This can lead to an out-of-bounds read from the dm-bufio buffer, potentially resulti...
CVE-2026-80958
A flaw was found in the dm-pcache component of the Linux kernel. The tail-kset read operations, used by cachereplay, the writeback worker, and the garbage collection GC worker, incorrectly calculate the length of the data region. This error causes the system to read beyond the intended segment da...
CVE-2026-80957
A flaw was found in the dm-pcache component of the Linux kernel. A local attacker could exploit a vulnerability in the cachereplay function, which does not properly handle a forged last-kset chain. By crafting a malicious chain that points back to an already visited segment, an attacker can cause...
CVE-2026-80961
A flaw was found in the dm-pcache component of the Linux kernel. A local attacker with CAPSYSADMIN capabilities could exploit unbounded fields decoded from the cache device. This could lead to an out-of-bounds read, potentially disclosing sensitive information from adjacent persistent memory to...
CVE-2026-80955
A flaw was found in the Linux kernel's dm-pcache component. This vulnerability, a use-after-free, occurs within the ksetreplay function when a stale key's segment generation is accessed after it has been freed. This could allow a local attacker to potentially cause a system crash or lead to other...
DEBIAN-CVE-2026-89578
In the Linux kernel, the following vulnerability has been resolved: dm-io: clone the source bio instead of copying its biovec For DMIOBIO requests, doregion built each destination bio by walking the source bio's biovec and re-adding the pages one at a time, tracking the remaining transfer in...
CVE-2026-89578
In the Linux kernel, the following vulnerability has been resolved: dm-io: clone the source bio instead of copying its biovec For DMIOBIO requests, doregion built each destination bio by walking the source bio's biovec and re-adding the pages one at a time, tracking the remaining transfer in...
CVE-2026-89573
In the Linux kernel, the following vulnerability has been resolved: dm array: reject an array block whose value size is not the caller's arrayblockcheck can only compare the header against itself, so a block with valuesize 4 and maxentries 1018 is internally consistent and passes. dm-cache keeps...
DEBIAN-CVE-2026-89573
In the Linux kernel, the following vulnerability has been resolved: dm array: reject an array block whose value size is not the caller's arrayblockcheck can only compare the header against itself, so a block with valuesize 4 and maxentries 1018 is internally consistent and passes. dm-cache keeps...
CVE-2026-89577
In the Linux kernel, the following vulnerability has been resolved: dm-io: report non-retryable errors separatedly The error codes BLKSTSNOTSUPP and BLKSTSINVAL should not cause leg failure on dm-raid1. This patch changes the interface to dm-io, so that it reports two error bitmaps - errorbits an...
DEBIAN-CVE-2026-89574
In the Linux kernel, the following vulnerability has been resolved: dm array: validate array block headers on read arrayblockcheck validates blocknr and csum and nothing else, while nodecheck, next to it, has bounded the structural fields since both were written. dmarraycursornext takes its loop...