CVE-2026-68172

HIGHPre-NVD 7.17.1
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: 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:

arm64: make huge_ptep_get handled unaligned addresses

huge_ptep_get() can be handed a virtual address pointing to the middle of a contpmd/contpte mapped hugetlb folio (examples of callers are pagemap_hugetlb_range, page_mapped_in_vma).

The arm64 helper rewalks the pgtables in find_num_contig to answer whether the huge pte we have maps a contpmd or a contpte hugetlb folio, and returns CONT_PMDS or CONT_PTES, so that it can collect a/d bits over the contiguous ptes. We can falsely return CONT_PTES instead of CONT_PMDS if the addr is not aligned. On systems where CONT_PTES != CONT_PMDS (meaning page size is 16K), we could collect excess A/D bit state, meaning extra work for the kernel. Even worse, we may iterate beyond the PTE table and dereference a garbage ptep pointer to access physical memory we don't own. Since the ptep pointer is a linear map address, we may run off the end of the linear map or into a hole, dereference a VA not mapped into the kernel pgtables and cause kernel panic.

Fix this by aligning the pmdp pointer down to a contpmd base before checking equality with the passed huge pte pointer, to correctly answer whether the huge pte is the base of a contpmd block.

CVSS v3
7.1
EG Score
7.1(high)
EG Risk
37(Track)
EG Risk 37/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (3)

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

arm64: make huge_ptep_get handled unaligned addresses - kernel/git/stable/linux.git - Linux kernel stable tree

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

arm64: make huge_ptep_get handled unaligned addresses - kernel/git/stable/linux.git - Linux kernel stable tree

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

arm64: make huge_ptep_get handled unaligned addresses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9cd4b1a52eff330798d668c1775f8bc450776280

Vendor Advisories for CVE-2026-68172(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 32× in last 7d / 39× 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 10:44 UTCGHSA enrichment
  2. 2026-08-19 22:05 UTCEG score recompute
  3. 2026-08-19 22:04 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 09:24 UTCGHSA enrichment
  6. 2026-08-18 20:44 UTCEG score recompute
  7. 2026-08-18 20:44 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-18 08:03 UTCGHSA enrichment
  10. 2026-08-17 19:20 UTCEG score recompute
  11. 2026-08-17 19:20 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 05:40 UTCEG score recompute
  14. 2026-08-17 05:40 UTCGHSA enrichment
  15. 2026-08-17 05:10 UTCEG score recompute
  16. 2026-08-17 05:10 UTCGHSA enrichment
  17. 2026-08-17 03:33 UTCEG score recompute
  18. 2026-08-17 03:33 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 14:53 UTCGHSA enrichment
  21. 2026-08-16 02:13 UTCGHSA enrichment
  22. 2026-08-15 13:34 UTCEG score recompute
  23. 2026-08-15 13:34 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-15 00:49 UTCGHSA enrichment
Show 14 more
  1. 2026-08-14 12:09 UTCEG score recompute
  2. 2026-08-14 12:09 UTCGHSA enrichment
  3. 2026-08-13 23:30 UTCEG score recompute
  4. 2026-08-13 23:30 UTCGHSA enrichment
  5. 2026-08-13 22:45 UTCEG score recompute 7.10
  6. 2026-08-13 22:45 UTCGHSA enrichment
  7. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-13 18:29 UTCEG score recompute
  10. 2026-08-13 18:29 UTCGHSA enrichment
  11. 2026-08-12 13:51 UTCEPSS rescore
  12. 2026-08-10 13:24 UTCNVD update
  13. 2026-08-10 12:20 UTCEG score recompute
  14. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68172?
CVE-2026-68172 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: arm64: make hugeptepget handled unaligned addresses hugeptepget() can be handed a virtual address pointing to the middle of a contpmd/contpte mapped hugetlb folio (examples of callers are pagemaphugetlbrange, pagemappedin_vma). The…
When was CVE-2026-68172 disclosed?
CVE-2026-68172 was first published in the National Vulnerability Database on August 10, 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-68172 actively exploited?
CVE-2026-68172 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.6% of all scored CVEs.
What is the CVSS score of CVE-2026-68172?
CVE-2026-68172 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-68172?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68172, 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-68172

Explore →

Is Your Infrastructure Affected by CVE-2026-68172?

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