CVE-2026-72102

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

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-72102 dm_early_create: fix freeing used table on dm_resume failure

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

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

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

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

CVE-2026-72100 dm-integrity: fix a bug if the bio is out of limits

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

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