Vulnerability · Published Aug 10, 2026 · Assigned by Linux

CVE-2026-68172arm64: make huge_ptep_get handled unaligned addresses

High 7.1

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 5% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.1High
Exploit odds (30 days)0.2%top 94.6% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:14linux7.1.6-1DEBIAN-CVE-2026-68172
Ubuntu:26.04:LTSlinux7.0.0-38.38UBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-68172
Ubuntu:26.04:LTSlinux-aws7.0.0-1014.14UBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-aws-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-68172
Ubuntu:26.04:LTSlinux-azure7.0.0-1017.17UBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-azure-7.07.0.0-1017.17~24.04.1UBUNTU-CVE-2026-68172
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1016.16UBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-azure-fde-7.07.0.0-1016.16~24.04.1UBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-68172
Ubuntu:26.04:LTSlinux-gcp7.0.0-1014.14UBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-gcp-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-68172
Ubuntu:26.04:LTSlinux-gke7.0.0-1008.9UBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-38.38~24.04.4UBUNTU-CVE-2026-68172
Ubuntu:26.04:LTSlinux-ibm7.0.0-1015.15UBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-68172
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-nvidia-7.07.0.0-1024.25~24.04.1UBUNTU-CVE-2026-68172
Ubuntu:26.04:LTSlinux-nvidia-bos7.0.0-2022.23UBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-68172
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1015.15UBUNTU-CVE-2026-68172
Ubuntu:26.04:LTSlinux-oracle7.0.0-1013.13UBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-oracle-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-68172
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-68172
Ubuntu:26.04:LTSlinux-realtime7.0.0-38.38.1UBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-68172
Ubuntu:26.04:LTSlinux-riscv7.0.0-38.38.1UBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-68172
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-38.38.1~24.04.1UBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-68172
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-68172

Affected products (as reported)

VendorProductVersions
Linux Linux 29cb80519689706387bde47000dbb2ed91143063 – before 9cd4b1a52eff330798d668c1775f8bc45077628029cb80519689706387bde47000dbb2ed91143063 – before f3530aec26563f4d483ff31402392961362e9bc629cb80519689706387bde47000dbb2ed91143063 – before f73a8edc2ccc6ec72c37d5c578e7592d2e1f9922
Linux Linux 6.16

References