In the Linux kernel, a logic error in the dm-integrity block device driver causes the internal hash_offset variable to be incremented twice. The second increment occurs after it has already been advanced in the data copy loop, leading to an incorrect hash calculation. It is inferred that this incorrect hash may cause integrity checks to fail or to incorrectly accept tampered data, potentially allowing a malicious actor to modify block device contents without detection and undermine data authenticity. This weakness is a software logic flaw resulting in incorrect state management during integrity verification (CWE‑665, CWE‑703).

The vulnerability affects the Linux kernel dm‑integrity driver. No specific kernel version is mentioned, so the defect could potentially exist in any kernel branch before the fix. Affected systems are all Linux distributions running a kernel that has not yet applied the patch for this issue.

The EPSS score is < 1%, indicating a low exploitation probability, and the bug is not listed in CISA KEV. The CVSS score is 7.1, reflecting a high severity, but the flaw directly compromises data integrity. Based on the description, it is inferred that the likely attack vector is local or privileged, requiring the attacker to write to a dm‑integrity‑backed block device or influence kernel memory. Successful exploitation would let the attacker modify data while bypassing integrity checks, potentially compromising applications that rely on dm‑integrity for protection. The risk is primarily to data integrity rather than code execution or denial of service.