dm-integrity: don't increment hash_offset twice
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.
- Published
- Aug 15, 2026
- Updated
- Aug 23, 2026
- EPSS
- 0.6% · 45th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.7affected
- 84597a44a9d86ac949900441cea7da0af0f2f473 and later · before c66b1781a54984227e94b862be9328d81d81e51caffected · git
- 84597a44a9d86ac949900441cea7da0af0f2f473 and later · before 39697e2759ac23e65361fe61482f8174cad8a752affected · git
- 84597a44a9d86ac949900441cea7da0af0f2f473 and later · before e6646f4d711d74930d39cce6fb7bfcae4cbee5fdaffected · git
- 84597a44a9d86ac949900441cea7da0af0f2f473 and later · before cf9feed8c131e303ecf2afebe6f791be018818adaffected · git
- 84597a44a9d86ac949900441cea7da0af0f2f473 and later · before 4f4e43337e9ef322595201cfc24def50fd624219affected · git
- 84597a44a9d86ac949900441cea7da0af0f2f473 and later · before 5dfd8042635278613da3b88553e25ade2103cd58affected · git
- 84597a44a9d86ac949900441cea7da0af0f2f473 and later · before 829476c06496aab018f14127c055adb164d1a750affected · git
- 84597a44a9d86ac949900441cea7da0af0f2f473 and later · before edf025f083854f80032b73a1aad69a3c90db236faffected · git
- before 5.7not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 39697e2759ac23e65361fe61482f8174cad8a752 | Vendor (CNA) |
| Linux Linux | 4f4e43337e9ef322595201cfc24def50fd624219 | Vendor (CNA) |
| Linux Linux | 5dfd8042635278613da3b88553e25ade2103cd58 | Vendor (CNA) |
| Linux Linux | 829476c06496aab018f14127c055adb164d1a750 | Vendor (CNA) |
| Linux Linux | c66b1781a54984227e94b862be9328d81d81e51c | Vendor (CNA) |
| Linux Linux | cf9feed8c131e303ecf2afebe6f791be018818ad | Vendor (CNA) |
| Linux Linux | e6646f4d711d74930d39cce6fb7bfcae4cbee5fd | Vendor (CNA) |
| Linux Linux | edf025f083854f80032b73a1aad69a3c90db236f | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- Low
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
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
Vendor advisories and official records. Exploit/PoC links are deliberately left out.