# CVE-2026-64520: firmware: arm_ffa: Bound PARTITION_INFO_GET_REGS copies

> A missing bounds check in the Linux kernel's ARM FFA driver allows out-of-bounds writes, potentially leading to code execution or privilege escalation.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jul 2026
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2026-64520, DEBIAN-CVE-2026-64520, GHSA-p6rc-3j29-m628, ROOT-OS-DEBIAN-13-CVE-2026-64520, ROOT-OS-UBUNTU-2204-CVE-2026-64520, UBUNTU-CVE-2026-64520

## What is CVE-2026-64520?

CVE-2026-64520 is a high-severity memory corruption vulnerability in Linux, published on 25 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

firmware: arm_ffa: Bound PARTITION_INFO_GET_REGS copies

The register-based PARTITION_INFO_GET path trusted the firmware-provided
indices when copying partition descriptors into the caller buffer.
Reject inconsistent counts or index progressions so the copy loop cannot
write past the allocated array.

(fixed cur_idx when exactly one descriptor in the first fragment)

## Which versions are affected by CVE-2026-64520?


## How do I fix CVE-2026-64520?

Apply the vendor's patch.

## Is CVE-2026-64520 being exploited?

There is no known exploitation of CVE-2026-64520 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64520 and fix it if it is affected.

What it is: CVE-2026-64520 is a high-severity memory corruption vulnerability in Linux, published on 25 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64520 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-64520/ (Markdown: https://insights.sbomify.com/CVE-2026-64520/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-64520
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-64520
- OSV: https://osv.dev/vulnerability/CVE-2026-64520

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-64520/
Summaries are generated and may contain mistakes; the official description above is the record.