VulnerabilityPublished 15 Aug 2026Updated 19 Oct 2026

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

Affects Linux kernelSource CVE Database V5

Not known to be exploited · CVSS 7.1 High · fixed in edf025f083854f80032b73a1aad69a3c90db236f : patch Linux kernel soon.

Data as of 26 Oct 2026, 13:07 UTC

CVSS 3.1 base score

7.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS

0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch

Available – fixed in edf025f083854f80032b73a1aad69a3c90db236f, e6646f4d711d74930d39cce6fb7bfcae4cbee5fd, cf9feed8c131e303ecf2afebe6f791be018818ad +5

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 84597a44a9d86ac949900441cea7da0af0f2f473, < edf025f083854f80032b73a1aad69a3c90db236f	Fixed in edf025f083854f80032b73a1aad69a3c90db236f
LinuxLinux	Affected ≥ 84597a44a9d86ac949900441cea7da0af0f2f473, < e6646f4d711d74930d39cce6fb7bfcae4cbee5fd	Fixed in e6646f4d711d74930d39cce6fb7bfcae4cbee5fd
LinuxLinux	Affected ≥ 84597a44a9d86ac949900441cea7da0af0f2f473, < cf9feed8c131e303ecf2afebe6f791be018818ad	Fixed in cf9feed8c131e303ecf2afebe6f791be018818ad
LinuxLinux	Affected ≥ 84597a44a9d86ac949900441cea7da0af0f2f473, < c66b1781a54984227e94b862be9328d81d81e51c	Fixed in c66b1781a54984227e94b862be9328d81d81e51c
LinuxLinux	Affected ≥ 84597a44a9d86ac949900441cea7da0af0f2f473, < 829476c06496aab018f14127c055adb164d1a750	Fixed in 829476c06496aab018f14127c055adb164d1a750
LinuxLinux	Affected ≥ 84597a44a9d86ac949900441cea7da0af0f2f473, < 39697e2759ac23e65361fe61482f8174cad8a752	Fixed in 39697e2759ac23e65361fe61482f8174cad8a752

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.

CWE-682Incorrect Calculation (opens in a new tab)
Pillar weaknessLikelihood of exploit: High
The product performs a calculation that generates incorrect or unintended results that are later used in security-critical decisions or resource management.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Implementation
Understand your programming language's underlying representation and how it interacts with numeric calculation. Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, "not-a-number" calculations, and how your language handles numbers…
Implementation · Input Validation
Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range.
Implementation
Use the appropriate type for the desired action. For example, in C/C++, only use unsigned types for values that could never be negative, such as height, width, or other numbers related to quantity.
Attack patterns
Integer Attacks (opens in a new tab)
Pointer Manipulation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

WeaknessesCWE-682

Technical details

References

Community reviews

Related threats