Skip to content
Systems

CVE-2026-64467

8.8
High
EPSS 0.14%Patch availableJul 27, 2026

rust_binder refcount underflow on 32-bit Linux can cause kernel crash/use-after-free.

common questions

Is CVE-2026-64467 being exploited?

Not confirmed. CVE-2026-64467 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-64467?

CVE-2026-64467 is rated High with a CVSS score of 8.8. 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-64467?

Yes. A fix has been recorded for CVE-2026-64467. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-64467 affect?

CVE-2026-64467 affects Linux kernel (rust_binder component), 32-bit ARM Linux, Android devices with 32-bit kernels, Embedded/IoT devices using 32-bit Linux. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-64467?

Apply vendor kernel updates for 32-bit systems; restrict untrusted apps and reboot.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (rust_binder component)32-bit ARM LinuxAndroid devices with 32-bit kernelsEmbedded/IoT devices using 32-bit Linux
impact

Local unprivileged app can trigger refcount underflow in rust_binder on 32-bit kernels, causing use-after-free, kernel crash, and possible local privilege escalation.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= eafedbc7c050c44744fbdf80bdf3315e860b7513 and < 89b8cc948dce661af87527623b3a41cdd115e2f9
  • affected>= eafedbc7c050c44744fbdf80bdf3315e860b7513 and < 74920b1b4e474ba7a4de4323c0458deec49d210b
  • affected>= eafedbc7c050c44744fbdf80bdf3315e860b7513 and < 803c8a9502e9b97cd6ae937618ef4a8fd6274343
  • affected6.18
vendor says fixed in< 6.18, >= 6.18.39 and <= 6.18.*, >= 7.1.4 and <= 7.1.*, >= 7.2 and <= *

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free