SECUFOCUSNOW
Home›CVE index›CVE-2026-64318
Review reviewHigh

CVE-2026-64318

Linux

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 __be...

CVSS
7.1
EPSS
-
- percentile
CISA KEV
Not listed
Published
2026.07.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.1

Vulnerability overview

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 __be...

Affected product and versions

Product
Linux
Affected versions
>= 6ceea22bbbc84fcf6bf0913bb3db8a657e9002f6 < 09861651617ba0fec089e8b9477439e68398c110, >= 6ceea22bbbc84fcf6bf0913bb3db8a657e9002f6 < 5eacdb1967378f5e5591cd27a2d8cdee2df1a599, >= 6ceea22bbbc84fcf6bf0913bb3db8a657e9002f6 < b5e9c09309e18fd9839ad007c238120353ca0cc4, >= 6ceea22bbbc84fcf6bf0913bb3db8a657e9002f6 < fd94a779020f2ecc8b2607f4c20b34acb1763b9a, >= 6ceea22bbbc84fcf6bf0913bb3db8a657e9002f6 < 4671bb74bba05fdd4acf670a35758c29e8c97b83, >= 6ceea22bbbc84fcf6bf0913bb3db8a657e9002f6 < ce93228e2193a17d2c58b656e439bb39fe5c3af8, >= 6ceea22bbbc84fcf6bf0913bb3db8a657e9002f6 < 44f37ee92fdcd377c41bdf6a31cdd8cc7d4c410e, >= 6ceea22bbbc84fcf6bf0913bb3db8a657e9002f6 < 2dc0bfd2fe355fb930de63c2f2eb8ced8570c579, >= 3.11
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
CWE
Not available