CVE-2026-64080: firmware: arm_ffa: Snapshot notifier callbacks under lock
In the Linux kernel, the following vulnerability has been resolved:
firmware: arm_ffa: Snapshot notifier callbacks under lock
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.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory-safety flaw in ARM FF-A firmware notification handling. A race can let one thread remove a notifier while another still uses it, creating a use-after-free condition. The reported impact is critical, but the bundle does not show active exploitation.
Executive priority
Treat as urgent for affected ARM Linux environments because kernel memory corruption can cross privilege and trust boundaries. Patch validation should focus on systems allowing local users, workloads, containers, or app execution. No source in the bundle supports emergency response for active exploitation.
Technical view
The handlers find a notifier under notify_lock, release the lock, then dereference the notifier entry. Concurrent unregister can free that entry in the gap. The fix snapshots the callback pointer and callback data while locked, then invokes after unlock, preserving behavior while closing the stale-memory window.
Likely exposure
Exposure appears limited to Linux systems using ARM FF-A firmware notification paths and affected kernel versions or commits. Prioritize ARM-based fleets, devices, and environments where untrusted local code can run. The provided version data is incomplete and should be reconciled with vendor kernel packages.
Exploitation context
The CVSS vector is local, low complexity, no privileges, no user interaction, with high confidentiality, integrity, and availability impact. The source bundle says KEV is false and provides no cited evidence of in-the-wild exploitation or public exploit availability.
Researcher notes
The core issue is a lock lifetime bug: lookup under notify_lock, unlock, then stale pointer dereference after concurrent unregister. Analysis should verify both framework and non-framework notification paths received the snapshot-before-unlock pattern. The affected-version list in the bundle appears ambiguous, so avoid broad claims without vendor mapping.
Mitigation direction
Update to a kernel containing the referenced stable fixes.
Check Linux distribution or device-vendor advisories for backported packages.
Prioritize ARM systems using FF-A firmware features.
Restrict untrusted local code execution where patching is delayed.
Track vendor guidance because no standalone workaround is named.
Validation and detection
Inventory ARM Linux systems and kernel package versions.
Compare deployed kernels against vendor fixed builds or referenced commits.
Confirm whether ARM FF-A support is present in relevant builds.
Review change history for the notifier snapshot fix.
Monitor CVE and vendor advisories for revised affected-version data.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-64080 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.