Look up another CVE · open CVE-2026-64080 in the interactive tracker
CVE-2026-64080
firmware: arm_ffa: Snapshot notifier callbacks under lock
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-64080 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
Both notification handlers currently look up a notifier callback under notify_lock, drop the lock, and then dereference the returned notifier entry. A concurrent unregister can delete and free that entry in the gap, leaving the handler to dereference stale memory. Copy the callback pointer and callback data while notify_lock is still held and invoke the callback only after the lock is dropped. This keeps the existing callback execution model while removing the use-after-free window in both the framework and non-framework notification paths.
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
- 9.3 critical
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.20%, higher than 9.0% 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 | d1e38551fade |
| 6.15 | 7.0.11 | 0e7be42ef249 |
| 6.15 | 7.1 | 38290b180a4d |
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 through the Arm FF-A firmware notification IRQ/workqueue path (SMC/secure-partition notifications), not through any network protocol. Attackers reach it locally via secure-world FF-A traffic or TEE ioctl access on ARM64 TrustZone systems.
- AC:LAttack complexity, low
- This is a race where the attacker can flood FF-A notifications from secure world (or via concurrent TEE sessions) while driver teardown unregisters the callback; both sides of the race are attacker-influenceable on systems with OP-TEE async notifications enabled.
- PR:NPrivileges required, none
- A malicious secure-world partition can send FF-A notifications without any normal-world Linux credentials; the concurrent unregister side is reached automatically during kernel/driver teardown (reboot, shutdown, module unload) without requiring attacker privileges.
- UI:NUser interaction, none
- Exploitation requires no victim interaction beyond normal system operation; a malicious secure-world component or automated teardown events (scheduled reboot, OTA, shutdown) can trigger the race without the user performing any action.
- S:CScope, changed
- On Arm TrustZone deployments, a malicious secure-world partition can corrupt normal-world kernel memory across the secure/normal-world security boundary, escalating impact beyond the FF-A driver's own authority into full kernel compromise.
- C:HConfidentiality impact, high
- The UAF dereferences a freed kmalloc notifier entry containing callback metadata; stale heap contents can be read and leveraged for kernel memory disclosure consistent with UAF guidance.
- I:HIntegrity impact, high
- After the UAF, the handler invokes a function pointer read from freed memory (cb_info->cb/fwk_cb), enabling control-flow hijack and arbitrary kernel code execution via heap grooming.
- A:HAvailability impact, high
- The UAF can cause immediate kernel oops/panic from dereferencing freed memory or invoking a corrupted function pointer, satisfying kernel crash guidance for UAF bugs.