CVE-2026-64468

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

binder: fix UAF in binder_free_transaction()

In binder_free_transaction(), the t->to_proc is read under the t->lock. However, once the t->lock is dropped, the to_proc can die in parallel. This leads to a use-after-free error when we attempt to acquire its inner lock right afterwards:

================================================================== BUG: KASAN: slab-use-after-free in _raw_spin_lock+0xe4/0x1a0 Write of size 4 at addr ffff00001125da70 by task B/672

CPU: 20 UID: 0 PID: 672 Comm: B Not tainted 7.1.0-rc6-00284-g8e65320d91cd #4 PREEMPT Hardware name: linux,dummy-virt (DT) Call trace: _raw_spin_lock+0xe4/0x1a0 binder_free_transaction+0x8c/0x320 binder_send_failed_reply+0x21c/0x2f8 binder_thread_release+0x488/0x7e0 binder_ioctl+0x12c0/0x29a0 [...]

Allocated by task 675: __kmalloc_cache_noprof+0x174/0x444 binder_open+0x118/0xb70 do_dentry_open+0x374/0x1040 vfs_open+0x58/0x3bc [...]

Freed by task 212: __kasan_slab_free+0x58/0x80 kfree+0x1a0/0x4a4 binder_proc_dec_tmpref+0x32c/0x5e0 binder_deferred_func+0xc48/0x104c process_one_work+0x53c/0xbc0 [...] ==================================================================

To prevent this, pin the target thread (t->to_thread) to guarantee the target process remains alive. Undelivered transactions without a target thread are already safe, as the target process can only be the current context in those paths.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 25, 2026

Last Modified

July 27, 2026

Advisory Details (8)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

binder: fix UAF in binder_free_transaction() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f223d27a546c1e1f48d38fd67760e78f068fe8c4
generic

binder: fix UAF in binder_free_transaction() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d45ef513eed1abebfec90c3cfb6ae50c2a4182db
generic

binder: fix UAF in binder_free_transaction() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5602a43f251c3d75312df91a422675fc00ca3dce
generic

binder: fix UAF in binder_free_transaction() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/48aeda9f8039e4a6971d1804578efde7f2c01eda
generic

binder: fix UAF in binder_free_transaction() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/45df558c543bb5543bacc8065fd7c567740781e5
generic

binder: fix UAF in binder_free_transaction() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/328ccf32acb87e8bbb1fe2b065068c574e4db2bf
generic

binder: fix UAF in binder_free_transaction() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0f15f0f6ca5df566275ce517f257af2559528b41
generic

binder: fix UAF in binder_free_transaction() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0be901ab1dcc4af59b88f2e324493bb283850167

Vendor Advisories for CVE-2026-64468(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 15× in last 7d / 15× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 14:14 UTCEPSS rescore
  2. 2026-07-27 05:26 UTCEG score recompute
  3. 2026-07-27 05:26 UTCGHSA enrichment
  4. 2026-07-27 05:13 UTCEG score recompute 7.80
  5. 2026-07-27 05:13 UTCGHSA enrichment
  6. 2026-07-27 05:12 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 02:46 UTCEG score recompute
  10. 2026-07-26 02:46 UTCGHSA enrichment
  11. 2026-07-25 14:18 UTCEPSS rescore
  12. 2026-07-25 14:18 UTCEPSS rescore
  13. 2026-07-25 10:39 UTCNVD update
  14. 2026-07-25 09:26 UTCEG score recompute
  15. 2026-07-25 09:21 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64468?
CVE-2026-64468 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: binder: fix UAF in binderfreetransaction() In binderfreetransaction(), the t->to_proc is read under the t->lock. However, once the t->lock is dropped, the to_proc can die in parallel. This leads to a use-after-free error when we…
When was CVE-2026-64468 disclosed?
CVE-2026-64468 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64468 actively exploited?
CVE-2026-64468 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.6% of all scored CVEs.
What is the CVSS score of CVE-2026-64468?
CVE-2026-64468 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64468?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64468, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-64468

Explore →

Is Your Infrastructure Affected by CVE-2026-64468?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.