Linux: Incorrect Calculation
CVE-2026-72099 is a high-severity incorrect calculation vulnerability in Linux, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions c66b1781a54984227e94b862be9328d81d81e51c, 39697e2759ac23e65361fe61482f8174cad8a752, e6646f4d711d74930d39cce6fb7bfcae4cbee5fd as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.55% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to c66b1781a54984227e94b862be9328d81d81e51c or 39697e2759ac23e65361fe61482f8174cad8a752 or e6646f4d711d74930d39cce6fb7bfcae4cbee5fd or cf9feed8c131e303ecf2afebe6f791be018818ad, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 84597a44a9d86ac949900441cea7da0af0f2f473 up to, but not including, c66b1781a54984227e94b862be9328d81d81e51c; 84597a44a9d86ac949900441cea7da0af0f2f473 up to, but not including, 39697e2759ac23e65361fe61482f8174cad8a752; 84597a44a9d86ac949900441cea7da0af0f2f473 up to, but not including, e6646f4d711d74930d39cce6fb7bfcae4cbee5fd; 84597a44a9d86ac949900441cea7da0af0f2f473 up to, but not including, cf9feed8c131e303ecf2afebe6f791be018818ad; 84597a44a9d86ac949900441cea7da0af0f2f473 up to, but not including, 4f4e43337e9ef322595201cfc24def50fd624219; 84597a44a9d86ac949900441cea7da0af0f2f473 up to, but not including, 5dfd8042635278613da3b88553e25ade2103cd58; 84597a44a9d86ac949900441cea7da0af0f2f473 up to, but not including, 829476c06496aab018f14127c055adb164d1a750; 84597a44a9d86ac949900441cea7da0af0f2f473 up to, but not including, edf025f083854f80032b73a1aad69a3c90db236f; and 1 more ranges | c66b1781a54984227e94b862be9328d81d81e51c, 39697e2759ac23e65361fe61482f8174cad8a752, e6646f4d711d74930d39cce6fb7bfcae4cbee5fd, cf9feed8c131e303ecf2afebe6f791be018818ad, 4f4e43337e9ef322595201cfc24def50fd624219, 5dfd8042635278613da3b88553e25ade2103cd58 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L. Scored by CNA.
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Calculation
The product performs a calculation that generates incorrect or unintended results that are later used in security-critical decisions or resource management.
How developers prevent this class of flaw
- 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 that are too large or too small for its underlying representation.
- 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.
- 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.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
- git.kernel.org/stable/c/39697e2759ac23e65361fe61482f8174cad8a752
- git.kernel.org/stable/c/4f4e43337e9ef322595201cfc24def50fd624219
- git.kernel.org/stable/c/5dfd8042635278613da3b88553e25ade2103cd58
- git.kernel.org/stable/c/829476c06496aab018f14127c055adb164d1a750
- git.kernel.org/stable/c/c66b1781a54984227e94b862be9328d81d81e51c
- git.kernel.org/stable/c/cf9feed8c131e303ecf2afebe6f791be018818ad
- git.kernel.org/stable/c/e6646f4d711d74930d39cce6fb7bfcae4cbee5fd
- git.kernel.org/stable/c/edf025f083854f80032b73a1aad69a3c90db236f
Recent Incorrect Calculation vulnerabilities
- 8.6 High severity
- 7.8 High severity
- 9.8 Critical severity
- 8.1 High severity
- 7.5 High severity
- 8.6 High severity
Spotted an error? Tell us.