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

Greg Kroah-Hartman <[email protected]>
Newsgroups org.kernel.vger.linux-cve-announce
Message-ID <2026081524-CVE-2026-72099-30c0@gregkh>
From: Greg Kroah-Hartman <[email protected]>

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.

The Linux kernel CVE team has assigned CVE-2026-72099 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.7 with commit 84597a44a9d86ac949900441cea7da0af0f2f473 and fixed in 6.6.145 with commit cf9feed8c131e303ecf2afebe6f791be018818ad
	Issue introduced in 5.7 with commit 84597a44a9d86ac949900441cea7da0af0f2f473 and fixed in 6.12.97 with commit 4f4e43337e9ef322595201cfc24def50fd624219
	Issue introduced in 5.7 with commit 84597a44a9d86ac949900441cea7da0af0f2f473 and fixed in 6.18.40 with commit 5dfd8042635278613da3b88553e25ade2103cd58
	Issue introduced in 5.7 with commit 84597a44a9d86ac949900441cea7da0af0f2f473 and fixed in 7.1.5 with commit 829476c06496aab018f14127c055adb164d1a750
	Issue introduced in 5.7 with commit 84597a44a9d86ac949900441cea7da0af0f2f473 and fixed in 7.2-rc3 with commit edf025f083854f80032b73a1aad69a3c90db236f

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-72099
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/md/dm-integrity.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/cf9feed8c131e303ecf2afebe6f791be018818ad
	https://git.kernel.org/stable/c/4f4e43337e9ef322595201cfc24def50fd624219
	https://git.kernel.org/stable/c/5dfd8042635278613da3b88553e25ade2103cd58
	https://git.kernel.org/stable/c/829476c06496aab018f14127c055adb164d1a750
	https://git.kernel.org/stable/c/edf025f083854f80032b73a1aad69a3c90db236f
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.