Look up another CVE · open CVE-2026-64520 in the interactive tracker
CVE-2026-64520
firmware: arm_ffa: Bound PARTITION_INFO_GET_REGS copies
Published 2026-07-25 (3 months ago) by the Linux kernel CNA. Subsystem drivers/firmware. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-64520 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | vulnerable | 6.12.113-1 | No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication. |
| Debian 14forky | fixed | 7.0.12-1 | Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.12-1 | Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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)
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/firmware/arm_ffa/driver.c
- What this is
- FIRMWARE FRAMEWORK FOR ARMV8-AMAINTAINERS section matched on drivers/firmware/arm_ffa/ · linux-arm-kernel@lists.infradead.org · Maintained
Show whether Debian builds this, per release
Not established. This site could not find the build rule for the affected file in the kernel trees Debian ships, so it has no answer about whether Debian compiles this code. Read that as unknown, never as absent.
- bookworm, trixie, forky, sid?
- ?
- not established - no Makefile entry for the affected file
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS
Signals
- Published
- 2026-07-25 (3 months ago)source
- CVSS
- 8.4 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.13%, higher than 2.4% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/firmware
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.12 | 6.18.34 | f39bc7ebe75e |
| 6.12 | 7.0.11 | 79d95c02ae0a |
| 6.12 | 7.1 | 3974ea193840 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- Exploitation occurs through local SMC/HVC responses from the co-resident FF-A partition manager or hypervisor; no network, physical-device, or userspace path reaches the vulnerable parser.
- AC:LAttack complexity, low
- The responder controls both discovery responses and every fragment, allowing deterministic count mismatches, invalid indices, and non-progressing sequences without a race or condition outside its control.
- PR:NPrivileges required, none
- The malformed response is accepted automatically during kernel initialization without authentication or Linux credentials; the triggering firmware or hypervisor requires no privileges within the affected Linux instance.
- UI:NUser interaction, none
- Partition discovery executes automatically during FF-A initialization, so exploitation requires no victim action.
- S:UScope, unchanged
- The vulnerable driver and the corrupted heap, stack, and control-flow resources are all within the same Linux kernel security authority.
- C:HConfidentiality impact, high
- Oversized fragments read beyond the register-result stack object, while exploitable heap corruption can provide kernel-memory disclosure primitives.
- I:HIntegrity impact, high
- The responder can repeatedly supply fully controlled 24-byte descriptors beyond the allocated array, enabling extensive heap corruption and potential control-flow hijacking.
- A:HAvailability impact, high
- Large or non-progressing indices can cause massive out-of-bounds writes, infinite processing, kernel faults, or panic.