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-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...

EUVD-2026-59057

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...

EUVD-2026-59058

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-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

Summary (CVE-2026-72099) In the Linux kernel, the dm-integrity component had an issue where hash_offset could be incremented twice; the loop already increments hash_offset, so a second increment was unnecessary. The vulnerability was resolved by correcting this behavior in the relevant code path ...

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-72100

CVE-2026-72100 concerns the Linux kernel function dm-integrity. A bug in dm_integrity_check_limits could exit with DM_MAPIO_KILL while the affected range was still locked, causing a potential deadlock and leaked resources. The fix moves the limit check up so that on exit no resources are leaked. ...

CVE-2026-72098

The CVE-2026-72098 issue affects the Linux kernel’s dm-verity FEC calculation. A buffer overflow occurs in dm-verity-fec when computing erasures: if (neras && *neras fec->roots) fio->erasures[(*neras)++] = i;. The post-increment can push *neras to roots+1, which is passed as no_eras to deco...

EUVD-2026-59055

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-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-72096 dm-verity: make error counter atomic

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-72097

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-72097

CVE-2026-72097 involves the Linux kernel, fixing a possible NULL pointer dereference in dm-verity, occurring in dm_verity_loadpin_is_bdev_trusted when a device has no table. The document set does not provide exploitation details; it simply notes the fix. Patches are referenced in kernel.org commi...

EUVD-2026-59054

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-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

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-72094 dma-buf: dma-fence: Fix potential NULL pointer dereference

In the Linux kernel, the following vulnerability has been resolved: dma-buf: dma-fence: Fix potential NULL pointer dereference The commit mentioned in the fixes tag below introduced a mechanism through which fence producers can fully decouple from fence consumers. This, desirable, mechanism is...