CVE-2026-64318

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

CVE-2026-64318 is fixed in 2 products on 1 platform, first by DEBIAN-CVE-2026-64318, released July 26, 2026. It is not reported as exploited. Patch Radar priority: High.

High
CVSS
7.1
Moderate
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0016
5th percentile

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.

Where it's fixed

ProductFixed inFixReleased
Linux
linux · Debian 12.15 (bookworm) 6.1.180-1 DEBIAN-CVE-2026-64318 Jul 26, 2026
linux · Debian 13.5 (trixie) 6.12.96-1 DEBIAN-CVE-2026-64318 Jul 26, 2026
linux · Debian 14 7.1.4-1 DEBIAN-CVE-2026-64318 Jul 26, 2026
linux-6.12 · Debian 12.15 (bookworm) 6.12.100-1~deb12u1 DEBIAN-CVE-2026-64318 Jul 26, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.