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.
Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. A secondary CVSS source baseline 7.1; sources differ by 0.0.
A fix is available — apply it.
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.
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
August 15, 2026
August 23, 2026
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Red Hat Security Advisory: kernel security, bug fix, and enhancement update
Red Hat Security Advisory: kernel security, bug fix, and enhancement update
Red Hat Security Advisory: kernel-rt security, bug fix, and enhancement update
In the Linux kernel, the following vulnerability has been resolved: dm-integrity: don't...
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | kernel-rt-0:4.18.0-553.170.1.rt7.511.el8_10 | 2026-09-30 | redhat |
| redhat | kernel-0:4.18.0-553.170.1.el8_10 | 2026-09-30 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | 6.1.106-1 ... 6.1.99-1 (56 versions) |
| — |
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | 6.12.38-1 ... 6.12.96-1 (31 versions) |
| — |
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | 6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions) |
| — |
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 192 total refreshes for this CVE.
redhat:RHSA-2026:74132
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-72099
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.