Look up another CVE · open CVE-2026-64081 in the interactive tracker
CVE-2026-64081
firmware: arm_ffa: Validate framework notification message layout
Published 2026-07-19 (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-64081 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 | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| 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
Framework notifications carry an indirect message in the shared RX buffer. Validate the reported offset and size before using them, reject zero-length payloads, and ensure that any non-header payload starts at the UUID field rather than in the middle of the message header. Use the validated offset and size values for both kmemdup() and the UUID parsing path so malformed firmware data cannot drive an out-of-bounds read or an oversized allocation.
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-19 (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.19%, higher than 8.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.15 | 6.18.34 | 3c51d99449dc |
| 6.15 | 7.0.11 | 76eb90e2b03d |
| 6.15 | 7.1 | 4a1cc9e96b31 |
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
- The bug is reached when the ARM FF-A partition manager delivers a framework RX-buffer-full notification to the Linux host via per-CPU IRQ and SMCCC, not via network packets or physical device access.
- AC:LAttack complexity, low
- A malicious or compromised FF-A sender partition can craft the indirect message header offset and size fields directly in its TX buffer and reliably trigger the vulnerable kmemdup path on delivery.
- PR:NPrivileges required, none
- No Linux credentials, capabilities, or user-namespace privileges are checked or required on the vulnerable IRQ-driven path; exploitation only requires the ability to send a crafted FF-A indirect message from a peer partition or firmware.
- UI:NUser interaction, none
- Processing is automatic once the framework delivers the notification and fills the shared RX buffer; no victim user action is needed.
- S:UScope, unchanged
- The impact is kernel memory disclosure and denial of service within the host kernel security authority, not a VM escape or cross-IOMMU boundary bypass.
- C:HConfidentiality impact, high
- Unvalidated offset and size allow kmemdup to copy attacker-chosen amounts of kernel memory beyond the bounded RX buffer, constituting an out-of-bounds read of kernel memory.
- I:HIntegrity impact, high
- The attacker-controlled out-of-bounds copy primitive reads adjacent kernel objects and is a standard building block for kernel exploit chains that achieve arbitrary write and code execution.
- A:HAvailability impact, high
- Crafted values can cause kernel faults on invalid addresses during the out-of-bounds copy, or massive kmemdup allocations that exhaust kernel memory and crash or deny service.