Affects the Linux kernel notifier path on ARM; kernel vulnerabilities can impact broad infrastructure and enable system compromise across many Linux deployments.
CVE-2026-64080
Use-after-free in Linux kernel ARM firmware notifier can lead to kernel compromise.
Is CVE-2026-64080 being exploited?
Not confirmed. CVE-2026-64080 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.14% probability of exploitation in the next 30 days.
How severe is CVE-2026-64080?
CVE-2026-64080 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-64080?
Yes. A fix has been recorded for CVE-2026-64080. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64080 affect?
CVE-2026-64080 affects Linux kernel (arm_ffa firmware notifier), ARM FF-A platforms, Devices running Linux on ARM. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64080?
Apply vendor/kernel updates or backported patches immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Kernel use-after-free in firmware notifier can cause memory corruption leading to local privilege escalation, kernel code execution, or DoS.
Immediate action required
- affected>= 285a5ea0f542db94c3ed11e01a71abb47d15cbf5 and < d1e38551fadea230649bc428f0f35c9ee062a072
- affected>= 285a5ea0f542db94c3ed11e01a71abb47d15cbf5 and < 0e7be42ef2490f19d859a6146324d48cafdc9d5c
- affected>= 285a5ea0f542db94c3ed11e01a71abb47d15cbf5 and < 38290b180a4d5746baed796d49f88d56d2f336cd
- affected6.15
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.