dbcve.org
VulnerabilityAwaiting classification

CVE-2026-64080

CRITICAL · 9.3 CVSS v3.1 Published 2026-07-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
98/100
Remediation priority · Urgent
No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Use-after-free vulnerability in Linux kernel's ARM FFU (Firmware Framework for Arm) driver where notification handlers look up notifier callbacks under a lock, drop the lock, then dereference the callback entry. A concurrent unregister can free the entry in the gap, leading to stale memory dereference. The fix copies callback pointers while the lock is still held and invokes callbacks only after releasing the lock.

MitigationApply the kernel patch that copies callback pointers and data while notify_lock is held, invoking callbacks only after lock release. This eliminates the use-after-free window in both framework and non-framework notification paths.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify system architecture
    Run 'uname -m' or check /proc/cpuinfo to confirm ARM64 (aarch64) architecture
    Affected if System is not ARM64 - the arm_ffa driver only applies to ARM64 systems
  2. Check if arm_ffa driver is loaded
    Run 'lsmod | grep -i ffa' or check 'ls /sys/module/ | grep -i ffa' to see if the arm_ffa or arm_ffa_driver module is loaded
    Affected if arm_ffa module is not loaded - the driver must be present for the vulnerability to apply
  3. Verify FF-A firmware is active
    Check for presence of FF-A device nodes: 'ls /dev/ffa*' or check /sys/bus/platform/devices/*ffa* or inspect dmesg for 'ffa' or 'firmware: arm,ffa' messages
    Affected if FF-A firmware interface is not enumerated or active on the system
  4. Check kernel version
    Run 'uname -r' to get the running kernel version
    Affected if Kernel version is older than the version that includes the fix for CVE-2026-64080 - compare against the version that contains the patch copying callback pointers under notify_lock
  5. Verify patch presence in kernel source (if accessible)
    If kernel source is available, check the arm_ffa driver code in drivers/firmware/arm_ffa/*.c for the fix: look for code that copies callback pointers while holding notify_lock before invocation, rather than holding the lock through dereference
    Affected if The vulnerable code pattern still exists - where notifier entries are dereferenced after notify_lock is released

System is affected only if it runs an unpatched Linux kernel on ARM64 with the arm_ffa driver loaded and FF-A firmware actively in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the kernel patch that copies callback pointers and data while notify_lock is held, invoking callbacks only after lock release. This eliminates the use-after-free window in both framework and non-framework notification paths.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,150
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-64080 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-64080 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data