CVE-2026-72099

Received Received - Intake

dm-integrity hash_offset double increment vulnerability

Publication date: 2026-08-15

Last updated on: 2026-08-23

Assigner: kernel.org

Description

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

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-15

Last Modified

2026-08-23

Generated

2026-09-04

AI Q&A

2026-08-15

EPSS Evaluated

2026-09-03

NVD

CVE-2026-72099

EUVD

EUVD-2026-59057

Affected Vendors & Products

Vendor	Product	Version / Range
linux_kernel	linux_kernel	*
linux	kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This is a Linux kernel vulnerability in the dm-integrity component. It involves an issue where the hash_offset variable is incorrectly incremented twice in a loop, which could lead to memory corruption or undefined behavior in the integrity checking mechanism of device-mapper.

Detection Guidance

This vulnerability is specific to the Linux kernel's dm-integrity module and does not have a direct network detection method. To check if your system is affected, verify the kernel version and whether the dm-integrity module is in use. Commands like 'uname -r' and 'lsmod | grep dm_integrity' can help identify the kernel and module status.

Impact Analysis

If exploited, this flaw could cause system instability, data corruption, or crashes in systems using dm-integrity for storage integrity checks. It may also allow privilege escalation if an attacker gains control of the affected system.

Mitigation Strategies

Update the Linux kernel to the latest patched version to resolve the dm-integrity hash_offset vulnerability. Check your distribution's security advisories for kernel updates and apply them immediately.

Hi! I’m here to help you understand CVE-2026-72099. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70