CVE-2026-72107

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

dm era: fix out-of-bounds memory access for non-zero start sector

dm-era tracks writes in target-relative blocks, but era_map() calculates the writeset block before applying the target offset. Tables with a non-zero start sector can therefore pass an absolute mapped-device block to metadata_current_marked().

If the absolute block is beyond the current writeset size, writeset_marked() tests past the end of the in-core bitset. KASAN reports this as a vmalloc-out-of-bounds access.

Apply the target offset before calculating the era block so writeset lookups use the target-relative block number.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

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).

How it’s computed
Severity88% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (8)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

dm era: fix out-of-bounds memory access for non-zero start sector - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fe94a0b14010a3c267ff9a2508afb4f27ff1c5bf
generic

dm era: fix out-of-bounds memory access for non-zero start sector - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e3ffa8e492e5cdee62d916ee3e9244ccce2b73c5
generic

dm era: fix out-of-bounds memory access for non-zero start sector - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/db5f9b4601f0012038e5a2628aedec2f47933380
generic

dm era: fix out-of-bounds memory access for non-zero start sector - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bafe3e720cdac38cd7ea4eb7852a8f2dbe1bbfe6
generic

dm era: fix out-of-bounds memory access for non-zero start sector - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a868196f03c2b19418ae3d2b69e195d668a271e5
generic

dm era: fix out-of-bounds memory access for non-zero start sector - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9946a7176bd8c25ddd6e5f1799c54e572ee6bf0f
generic

dm era: fix out-of-bounds memory access for non-zero start sector - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7e1822f83c5a1ee7b4a19e98edde8770a10b4c71
generic

dm era: fix out-of-bounds memory access for non-zero start sector - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1fcb5e29dd7a5b85adb9d8b539911741d878e829

Vendor Advisories for CVE-2026-72107(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 29× in last 7d / 29× in last 30d)

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.

  1. 2026-08-20 17:40 UTCGHSA enrichment
  2. 2026-08-20 06:03 UTCGHSA enrichment
  3. 2026-08-19 18:25 UTCEG score recompute
  4. 2026-08-19 18:25 UTCGHSA enrichment
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-19 05:57 UTCGHSA enrichment
  7. 2026-08-18 18:18 UTCEG score recompute
  8. 2026-08-18 18:17 UTCGHSA enrichment
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 06:39 UTCGHSA enrichment
  12. 2026-08-17 19:02 UTCEG score recompute
  13. 2026-08-17 19:01 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 06:21 UTCEG score recompute
  16. 2026-08-17 06:21 UTCGHSA enrichment
  17. 2026-08-17 06:00 UTCEG score recompute▲ 8.80
  18. 2026-08-17 06:00 UTCGHSA enrichment
  19. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  20. 2026-08-17 05:33 UTCEG score recompute
  21. 2026-08-17 05:33 UTCGHSA enrichment
  22. 2026-08-17 05:25 UTCMITRE cvelistV5
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 02:15 UTCEPSS rescore
Show 4 more
  1. 2026-08-15 06:43 UTCGHSA enrichment
  2. 2026-08-15 06:23 UTCNVD update
  3. 2026-08-15 06:12 UTCEG score recompute
  4. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72107?
CVE-2026-72107 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: dm era: fix out-of-bounds memory access for non-zero start sector dm-era tracks writes in target-relative blocks, but era_map() calculates the writeset block before applying the target offset. Tables with a non-zero start sector…
When was CVE-2026-72107 disclosed?
CVE-2026-72107 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72107 actively exploited?
CVE-2026-72107 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.4% of all scored CVEs.
What is the CVSS score of CVE-2026-72107?
CVE-2026-72107 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-72107?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72107, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72107

Explore →

Is Your Infrastructure Affected by CVE-2026-72107?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs