CVE-2026-72103

CVE-2026-72103 relates to the Linux kernel’s dm-crypt flow. A refactoring bug caused the caller’s thread keyring to be kept alive beyond the caller’s lifetime, making the LUKS volume key linger in memory. As a result, cryptsetup luksSuspend could fail to wipe the key, even though luksOpen passes ...

CVE-2026-72103 dm: avoid leaking the caller's thread keyring via the table device file

In the Linux kernel, the following vulnerability has been resolved: dm: avoid leaking the caller's thread keyring via the table device file The refactoring in commit a28d893eb327 "md: port block device access to file" accidentally causes the caller's thread keyring to be kept alive long beyond th...

CVE-2026-72103

In the Linux kernel, the following vulnerability has been resolved: dm: avoid leaking the caller's thread keyring via the table device file The refactoring in commit a28d893eb327 "md: port block device access to file" accidentally causes the caller's thread keyring to be kept alive long beyond th...

EUVD-2026-59060

In the Linux kernel, the following vulnerability has been resolved: dmearlycreate: fix freeing used table on dmresume failure If dmresume fails, the kernel attempts to free table with dmtabledestroy, but the table was already instantiated with dmswaptable. This commit skips the call to...

EUVD-2026-59061

In the Linux kernel, the following vulnerability has been resolved: dm: avoid leaking the caller's thread keyring via the table device file The refactoring in commit a28d893eb327 "md: port block device access to file" accidentally causes the caller's thread keyring to be kept alive long beyond th...

CVE-2026-72101

In the Linux kernel, the following vulnerability has been resolved: dm-integrity: fix leaking uninitialized kernel memory If hash size is less than device's tuple size, dm-integrity is supposed to zero the remaining space. There was a bug in the code that zeroing didn't work. This commit fixes it...

CVE-2026-72101 dm-integrity: fix leaking uninitialized kernel memory

In the Linux kernel, the following vulnerability has been resolved: dm-integrity: fix leaking uninitialized kernel memory If hash size is less than device's tuple size, dm-integrity is supposed to zero the remaining space. There was a bug in the code that zeroing didn't work. This commit fixes it...

CVE-2026-72101

The CVE-2026-72101 involves the Linux kernel dm‑integrity module. A bug caused zeroing of the remaining space to fail when the hash size was smaller than the device tuple size, leading to leaking uninitialized kernel memory. The issue has been fixed by a commit that corrects the zeroing behavior....

CVE-2026-72101 dm-integrity: fix leaking uninitialized kernel memory

In the Linux kernel, the following vulnerability has been resolved: dm-integrity: fix leaking uninitialized kernel memory If hash size is less than device's tuple size, dm-integrity is supposed to zero the remaining space. There was a bug in the code that zeroing didn't work. This commit fixes it...

EUVD-2026-59059

In the Linux kernel, the following vulnerability has been resolved: dm-integrity: fix leaking uninitialized kernel memory If hash size is less than device's tuple size, dm-integrity is supposed to zero the remaining space. There was a bug in the code that zeroing didn't work. This commit fixes it...

CVE-2026-72099

In the Linux kernel, the following vulnerability has been resolved: dm-integrity: don't increment hashoffset twice hashoffset is already incremented in the loop "for i = 0; i tocopy; i++, ts--". Do not increment it again...

CVE-2026-72100

In the Linux kernel, the following vulnerability has been resolved: dm-integrity: fix a bug if the bio is out of limits If dmintegritychecklimits fails, the code would exit with DMMAPIOKILL. However, the range would be already locked at this point, and it wouldn't be unlocked, resulting in a...

CVE-2026-72099 dm-integrity: don't increment hash_offset twice

In the Linux kernel, the following vulnerability has been resolved: dm-integrity: don't increment hashoffset twice hashoffset is already incremented in the loop "for i = 0; i tocopy; i++, ts--". Do not increment it again...

CVE-2026-72099 dm-integrity: don't increment hash_offset twice

In the Linux kernel, the following vulnerability has been resolved: dm-integrity: don't increment hashoffset twice hashoffset is already incremented in the loop "for i = 0; i tocopy; i++, ts--". Do not increment it again...

CVE-2026-72098

In the Linux kernel, the following vulnerability has been resolved: dm-verity: fix buffer overflow in FEC calculation There's a buffer overflow in dm-verity-fec: if neras && neras fec-roots fio-erasuresneras++ = i; This allows neras to reach roots + 1 the post-increment pushes it past roots. This...

CVE-2026-72096

In the Linux kernel, the following vulnerability has been resolved: dm-verity: make error counter atomic The error counter "v-corruptederrs" was not atomic, thus it could be subject to race conditions. The call to dmauditlogtarget"max-corrupted-errors" may be skipped due to the races...

CVE-2026-72097 dm-verity: fix a possible NULL pointer dereference

In the Linux kernel, the following vulnerability has been resolved: dm-verity: fix a possible NULL pointer dereference Fix a possible NULL pointer dereference dmverityloadpinisbdevtrusted if the device has no table...

CVE-2026-72095

The CVE-2026-72095 issue affects the Linux kernel dma_fence_dedup_array() function, which incorrectly returned 1 for a 0-length input, contradicting the documented contract. The bug could allow a zero local count path to reach a dedup call and dereference an uninitialized fence slot (notably in a...

CVE-2026-72095 dma-fence: Make dma_fence_dedup_array() robust against 0-count input

In the Linux kernel, the following vulnerability has been resolved: dma-fence: Make dmafencededuparray robust against 0-count input dmafencededuparray returns 1 when called with numfences == 0: the for-loop body never executes, j stays at 0, and the final return ++j yields 1. This contradicts bot...

CVE-2026-72095 dma-fence: Make dma_fence_dedup_array() robust against 0-count input

In the Linux kernel, the following vulnerability has been resolved: dma-fence: Make dmafencededuparray robust against 0-count input dmafencededuparray returns 1 when called with numfences == 0: the for-loop body never executes, j stays at 0, and the final return ++j yields 1. This contradicts bot...