CVE-2026-64469

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-25. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 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

A fix is available — apply it.

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

binder: fix UAF in binder_thread_release()

When a thread exits, binder_thread_release() walks its transaction stack to clear the t->from and t->to_proc that correspond with the exiting thread. However, a process dying in parallel might attempt to kfree some of these transactions. And if one of them has no associated t->to_proc, the t->to_proc->inner_lock will not be acquired.

This means that transaction accesses in binder_thread_release() after t->to_proc has been cleared might race with binder_free_transaction() and cause a use-after-free error as reported by KASAN:

================================================================== BUG: KASAN: slab-use-after-free in binder_thread_release+0x5d0/0x798 Write of size 8 at addr ffff000016627500 by task X/715

CPU: 17 UID: 0 PID: 715 Comm: X Not tainted 7.1.0-rc5-00149-g8fde5d1d47f6 #30 PREEMPT Hardware name: linux,dummy-virt (DT) Call trace: binder_thread_release+0x5d0/0x798 binder_ioctl+0x12c0/0x299c [...]

Allocated by task 717 on cpu 18 at 67.267803s: __kasan_kmalloc+0xa0/0xbc __kmalloc_cache_noprof+0x174/0x444 binder_transaction+0x554/0x8150 binder_thread_write+0xa30/0x4354 binder_ioctl+0x20f0/0x299c [...]

Freed by task 202 on cpu 18 at 90.416221s: __kasan_slab_free+0x58/0x80 kfree+0x1a0/0x4a4 binder_free_transaction+0x150/0x294 binder_send_failed_reply+0x398/0x6d8 binder_release_work+0x3e4/0x4ec binder_deferred_func+0xbd8/0x104c [...] ==================================================================

In order to avoid this, make sure that binder_free_transaction() reads the t->to_proc under the transaction lock. This will serialize the transaction release with the accesses in binder_thread_release(). Plus, it matches the documented locking rules for @to_proc.

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

August 17, 2026

Advisory Details (8)

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

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

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

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

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

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

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

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

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

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

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

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

https://git.kernel.org/stable/c/38e1a71728e5795b670cc159c18e286a40aeebb4
generic

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

https://git.kernel.org/stable/c/1f96f8c0a6ed4f6d01d3dd29ad0cbf08dde96082
generic

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

https://git.kernel.org/stable/c/114a116aaa5f0295376cdf12da743c5bce3b20ce

Vendor Advisories for CVE-2026-64469(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-15ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-15ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-15ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1—
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1—
linux-6.12—6.12.100-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (158 versions)7.1.4-1—

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 28× in last 7d / 100× 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.

Showing the most recent 100 of 194 total refreshes for this CVE.

  1. 2026-09-15 09:19 UTCEG score recompute
  2. 2026-09-15 09:19 UTCVendor advisory
  3. 2026-09-15 09:19 UTCGHSA enrichment
  4. 2026-09-14 10:16 UTCVendor advisory
  5. 2026-09-14 10:16 UTCGHSA enrichment
  6. 2026-09-13 21:23 UTCEG score recompute
  7. 2026-09-13 21:23 UTCVendor advisory
  8. 2026-09-13 21:23 UTCGHSA enrichment
  9. 2026-09-13 07:10 UTCVendor advisory
  10. 2026-09-13 07:09 UTCGHSA enrichment
  11. 2026-09-12 18:17 UTCEG score recompute
  12. 2026-09-12 18:17 UTCVendor advisory
  13. 2026-09-12 18:17 UTCGHSA enrichment
  14. 2026-09-12 05:13 UTCVendor advisory
  15. 2026-09-12 05:13 UTCGHSA enrichment
  16. 2026-09-11 16:20 UTCEG score recompute
  17. 2026-09-11 16:20 UTCVendor advisory
  18. 2026-09-11 16:20 UTCGHSA enrichment
  19. 2026-09-11 14:53 UTCEPSS rescore
  20. 2026-09-11 09:37 UTCEPSS rescore
  21. 2026-09-11 02:09 UTCVendor advisory
  22. 2026-09-11 02:09 UTCGHSA enrichment
  23. 2026-09-10 10:27 UTCEG score recompute
  24. 2026-09-10 10:27 UTCVendor advisory
  25. 2026-09-10 10:26 UTCGHSA enrichment
Show 75 more
  1. 2026-09-09 08:30 UTCEG score recompute
  2. 2026-09-09 08:30 UTCVendor advisory
  3. 2026-09-09 08:30 UTCGHSA enrichment
  4. 2026-09-08 22:01 UTCEPSS rescore
  5. 2026-09-07 21:12 UTCEG score recompute
  6. 2026-09-07 21:12 UTCVendor advisory
  7. 2026-09-07 21:11 UTCGHSA enrichment
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-07 00:01 UTCEG score recompute
  10. 2026-09-07 00:01 UTCGHSA enrichment
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 08:11 UTCGHSA enrichment
  13. 2026-09-05 19:18 UTCEG score recompute
  14. 2026-09-05 19:18 UTCGHSA enrichment
  15. 2026-09-05 15:31 UTCEPSS rescore
  16. 2026-09-05 05:56 UTCEG score recompute
  17. 2026-09-05 05:56 UTCGHSA enrichment
  18. 2026-09-04 12:38 UTCEG score recompute
  19. 2026-09-04 12:38 UTCGHSA enrichment
  20. 2026-09-04 05:07 UTCEPSS rescore
  21. 2026-09-02 14:12 UTCEPSS rescore
  22. 2026-09-01 23:08 UTCEG score recompute
  23. 2026-09-01 23:08 UTCGHSA enrichment
  24. 2026-09-01 13:54 UTCEPSS rescore
  25. 2026-09-01 04:40 UTCEPSS rescore
  26. 2026-08-31 01:48 UTCEG score recompute
  27. 2026-08-31 01:48 UTCGHSA enrichment
  28. 2026-08-30 19:17 UTCEPSS rescore
  29. 2026-08-30 12:55 UTCEG score recompute
  30. 2026-08-30 12:55 UTCGHSA enrichment
  31. 2026-08-30 01:22 UTCEPSS rescore
  32. 2026-08-30 00:02 UTCEG score recompute
  33. 2026-08-30 00:02 UTCGHSA enrichment
  34. 2026-08-28 21:42 UTCEPSS rescore
  35. 2026-08-28 03:39 UTCGHSA enrichment
  36. 2026-08-27 14:46 UTCEG score recompute
  37. 2026-08-27 14:46 UTCGHSA enrichment
  38. 2026-08-27 01:36 UTCEG score recompute
  39. 2026-08-27 01:35 UTCGHSA enrichment
  40. 2026-08-26 14:47 UTCEPSS rescore
  41. 2026-08-26 12:42 UTCGHSA enrichment
  42. 2026-08-25 23:35 UTCEG score recompute
  43. 2026-08-25 23:35 UTCGHSA enrichment
  44. 2026-08-25 13:49 UTCEPSS rescore
  45. 2026-08-25 10:41 UTCGHSA enrichment
  46. 2026-08-24 21:41 UTCEG score recompute
  47. 2026-08-24 21:41 UTCGHSA enrichment
  48. 2026-08-24 08:43 UTCGHSA enrichment
  49. 2026-08-23 19:47 UTCGHSA enrichment
  50. 2026-08-23 06:55 UTCEG score recompute
  51. 2026-08-23 06:55 UTCGHSA enrichment
  52. 2026-08-23 00:19 UTCEPSS rescore
  53. 2026-08-22 18:01 UTCGHSA enrichment
  54. 2026-08-22 05:07 UTCEG score recompute
  55. 2026-08-22 05:07 UTCGHSA enrichment
  56. 2026-08-21 23:49 UTCEPSS rescore
  57. 2026-08-21 16:14 UTCGHSA enrichment
  58. 2026-08-21 03:21 UTCEG score recompute
  59. 2026-08-21 03:21 UTCGHSA enrichment
  60. 2026-08-20 22:55 UTCEPSS rescore
  61. 2026-08-20 14:28 UTCGHSA enrichment
  62. 2026-08-20 00:12 UTCEG score recompute
  63. 2026-08-20 00:12 UTCGHSA enrichment
  64. 2026-08-19 17:04 UTCEPSS rescore
  65. 2026-08-19 11:17 UTCGHSA enrichment
  66. 2026-08-18 22:16 UTCEG score recompute
  67. 2026-08-18 22:16 UTCGHSA enrichment
  68. 2026-08-18 13:48 UTCEPSS rescore
  69. 2026-08-18 09:11 UTCGHSA enrichment
  70. 2026-08-17 20:17 UTCEG score recompute
  71. 2026-08-17 20:17 UTCGHSA enrichment
  72. 2026-08-17 13:47 UTCEPSS rescore
  73. 2026-08-17 05:43 UTCEG score recompute
  74. 2026-08-17 05:43 UTCGHSA enrichment
  75. 2026-08-17 05:16 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-64469?
CVE-2026-64469 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: binder: fix UAF in binderthreadrelease() When a thread exits, binderthreadrelease() walks its transaction stack to clear the t->from and t->to_proc that correspond with the exiting thread. However, a process dying in parallel might…
When was CVE-2026-64469 disclosed?
CVE-2026-64469 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64469 actively exploited?
CVE-2026-64469 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.7% of all scored CVEs.
What is the CVSS score of CVE-2026-64469?
CVE-2026-64469 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64469?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64469, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64469

Explore →

Is Your Infrastructure Affected by CVE-2026-64469?

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

Start Free Scan →Browse All CVEs