CVE-2026-64318

partitions: aix: bound the pp_count scan to the ppe array

HIGH
7.1
CVSS Score
Published: July 25, 2026 at 08:49 AM UTC
Updated: September 3, 2026 at 04:04 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.1
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: partitions: aix: bound the pp_count scan to the ppe array aix_partition() reads the physical volume descriptor into a fixed-size struct pvd and then scans its physical-partition-extent array: int numpps = be16_to_cpu(pvd->pp_count); ... for (i = 0; i < numpps; i += 1) { struct ppe *p = pvd->ppe + i; ... lp_ix = be16_to_cpu(p->lp_ix); pvd points at a single kmalloc()'d struct pvd whose ppe[] member holds a fixed ARRAY_SIZE(pvd->ppe) (1016) entries, but the loop runs up to the on-disk pp_count. pp_count is an unvalidated __be16 read straight from the descriptor, so a crafted AIX image with pp_count larger than 1016 drives the loop to read pvd->ppe[i] past the end of the allocation (up to 65535 entries, ~2 MB out of bounds). The partition scan runs without mounting anything, when a block device with a crafted AIX/IBM partition table appears (an attacker-supplied image attached with losetup -P, or a device auto-scanned by udev), via msdos_partition() -> aix_partition(). Clamp the scan to the number of entries the ppe[] array can hold.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.11 ≤ v < 5.10.2613.11 ≤ v < 5.15.2123.11 ≤ v < 6.1.1783.11 ≤ v < 6.12.963.11 ≤ v < 6.18.393.11 ≤ v < 6.6.1453.11 ≤ v < 7.1.43.11 ≤ v < 7.25.11 ≤ v < 5.15.2125.16 ≤ v < 6.1.1786.13 ≤ v < 6.18.396.19 ≤ v < 7.1.46.2 ≤ v < 6.6.1456.7 ≤ v < 6.12.963.116ceea22bbbc84fcf6bf0913bb3db8a657e9002f6
Vendor states this is fixed in 09861651617ba0fec089e8b9477439e68398c110 (fixed)
Vendor states this is fixed in 2dc0bfd2fe355fb930de63c2f2eb8ced8570c579 (fixed)
Vendor states this is fixed in 44f37ee92fdcd377c41bdf6a31cdd8cc7d4c410e (fixed)
Vendor states this is fixed in 4671bb74bba05fdd4acf670a35758c29e8c97b83 (fixed)
Vendor states this is fixed in 5eacdb1967378f5e5591cd27a2d8cdee2df1a599 (fixed)
Vendor states this is fixed in b5e9c09309e18fd9839ad007c238120353ca0cc4 (fixed)
Vendor states this is fixed in ce93228e2193a17d2c58b656e439bb39fe5c3af8 (fixed)
Vendor states this is fixed in fd94a779020f2ecc8b2607f4c20b34acb1763b9a (fixed)
Vendor states this is fixed in 3.11 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.96 (unaffected)
Vendor states this is fixed in 6.18.39 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.4 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

CVSS

7.1HIGHLinux
Vector?

Quick Info

StatusANALYZED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card