In the Linux kernel, the following vulnerability has been resolved: partitions: aix: bound the pp_count scan to the ppe array aix_partition() reads… (CVE-2026-64318)
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.
AI Analysis
Technical Summary
The Linux kernel's aix_partition() function reads the physical volume descriptor (pvd) into a fixed-size struct containing a physical-partition-extent (ppe) array of 1016 entries. However, it uses an unvalidated pp_count field from the on-disk descriptor to iterate over the ppe array, which can be up to 65535, leading to out-of-bounds reads beyond the allocated array. This vulnerability can be triggered when a crafted AIX partition table is detected by the kernel, such as when attaching a malicious image via losetup or during automatic scanning by udev. The fix bounds the scan loop to the actual size of the ppe array to prevent out-of-bounds access.
Potential Impact
An attacker can supply a crafted AIX partition table image that causes the kernel to read memory beyond the allocated bounds of the ppe array during partition scanning. This out-of-bounds read could potentially lead to information disclosure or kernel memory corruption. The vulnerability is triggered without mounting the filesystem, during device detection or setup. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to clamp the pp_count scan to the size of the allocated ppe array, preventing out-of-bounds reads. Users should apply the official kernel updates that include this patch once available. Since this is a kernel-level vulnerability, updating to a patched kernel version is the recommended remediation. Patch status is not yet confirmed in the provided data; check the Linux kernel vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: partitions: aix: bound the pp_count scan to the ppe array aix_partition() reads… (CVE-2026-64318)
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's aix_partition() function reads the physical volume descriptor (pvd) into a fixed-size struct containing a physical-partition-extent (ppe) array of 1016 entries. However, it uses an unvalidated pp_count field from the on-disk descriptor to iterate over the ppe array, which can be up to 65535, leading to out-of-bounds reads beyond the allocated array. This vulnerability can be triggered when a crafted AIX partition table is detected by the kernel, such as when attaching a malicious image via losetup or during automatic scanning by udev. The fix bounds the scan loop to the actual size of the ppe array to prevent out-of-bounds access.
Potential Impact
An attacker can supply a crafted AIX partition table image that causes the kernel to read memory beyond the allocated bounds of the ppe array during partition scanning. This out-of-bounds read could potentially lead to information disclosure or kernel memory corruption. The vulnerability is triggered without mounting the filesystem, during device detection or setup. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to clamp the pp_count scan to the size of the allocated ppe array, preventing out-of-bounds reads. Users should apply the official kernel updates that include this patch once available. Since this is a kernel-level vulnerability, updating to a patched kernel version is the recommended remediation. Patch status is not yet confirmed in the provided data; check the Linux kernel vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-499p-p84w-r6w8
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64318"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420d9c2644c7f8085cd9
Added to database: 07/25/2026, 23:09:01 UTC
Last enriched: 07/25/2026, 23:36:03 UTC
Last updated: 09/08/2026, 10:52:11 UTC
Views: 52
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.