CVE-2025-38176

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-07-04. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2025-20013 (ENISA EUVD) · GHSA-vmr3-mc6r-j34f (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

binder: fix use-after-free in binderfs_evict_inode()

Running 'stress-ng --binderfs 16 --timeout 300' under KASAN-enabled kernel, I've noticed the following:

BUG: KASAN: slab-use-after-free in binderfs_evict_inode+0x1de/0x2d0 Write of size 8 at addr ffff88807379bc08 by task stress-ng-binde/1699

CPU: 0 UID: 0 PID: 1699 Comm: stress-ng-binde Not tainted 6.14.0-rc7-g586de92313fc-dirty #13 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014 Call Trace: dump_stack_lvl+0x1c2/0x2a0 ? __pfx_dump_stack_lvl+0x10/0x10 ? __pfx__printk+0x10/0x10 ? __pfx_lock_release+0x10/0x10 ? __virt_addr_valid+0x18c/0x540 ? __virt_addr_valid+0x469/0x540 print_report+0x155/0x840 ? __virt_addr_valid+0x18c/0x540 ? __virt_addr_valid+0x469/0x540 ? __phys_addr+0xba/0x170 ? binderfs_evict_inode+0x1de/0x2d0 kasan_report+0x147/0x180 ? binderfs_evict_inode+0x1de/0x2d0 binderfs_evict_inode+0x1de/0x2d0 ? __pfx_binderfs_evict_inode+0x10/0x10 evict+0x524/0x9f0 ? __pfx_lock_release+0x10/0x10 ? __pfx_evict+0x10/0x10 ? do_raw_spin_unlock+0x4d/0x210 ? _raw_spin_unlock+0x28/0x50 ? iput+0x697/0x9b0 __dentry_kill+0x209/0x660 ? shrink_kill+0x8d/0x2c0 shrink_kill+0xa9/0x2c0 shrink_dentry_list+0x2e0/0x5e0 shrink_dcache_parent+0xa2/0x2c0 ? __pfx_shrink_dcache_parent+0x10/0x10 ? __pfx_lock_release+0x10/0x10 ? __pfx_do_raw_spin_lock+0x10/0x10 do_one_tree+0x23/0xe0 shrink_dcache_for_umount+0xa0/0x170 generic_shutdown_super+0x67/0x390 kill_litter_super+0x76/0xb0 binderfs_kill_super+0x44/0x90 deactivate_locked_super+0xb9/0x130 cleanup_mnt+0x422/0x4c0 ? lockdep_hardirqs_on+0x9d/0x150 task_work_run+0x1d2/0x260 ? __pfx_task_work_run+0x10/0x10 resume_user_mode_work+0x52/0x60 syscall_exit_to_user_mode+0x9a/0x120 do_syscall_64+0x103/0x210 ? asm_sysvec_apic_timer_interrupt+0x1a/0x20 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0xcac57b Code: c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 31 f6 e9 05 00 00 00 0f 1f 44 00 00 f3 0f 1e fa b8 RSP: 002b:00007ffecf4226a8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6 RAX: 0000000000000000 RBX: 00007ffecf422720 RCX: 0000000000cac57b RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00007ffecf422850 RBP: 00007ffecf422850 R08: 0000000028d06ab1 R09: 7fffffffffffffff R10: 3fffffffffffffff R11: 0000000000000246 R12: 00007ffecf422718 R13: 00007ffecf422710 R14: 00007f478f87b658 R15: 00007ffecf422830

Allocated by task 1705: kasan_save_track+0x3e/0x80 __kasan_kmalloc+0x8f/0xa0 __kmalloc_cache_noprof+0x213/0x3e0 binderfs_binder_device_create+0x183/0xa80 binder_ctl_ioctl+0x138/0x190 __x64_sys_ioctl+0x120/0x1b0 do_syscall_64+0xf6/0x210 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Freed by task 1705: kasan_save_track+0x3e/0x80 kasan_save_free_info+0x46/0x50 __kasan_slab_free+0x62/0x70 kfree+0x194/0x440 evict+0x524/0x9f0 do_unlinkat+0x390/0x5b0 __x64_sys_unlink+0x47/0x50 do_syscall_64+0xf6/0x210 entry_SYSCALL_64_after_hwframe+0x77/0x7f

This 'stress-ng' workload causes the concurrent deletions from 'binder_devices' and so requires full-featured synchronization to prevent list corruption.

I've found this issue independently but pretty sure that syzbot did the same, so Reported-by: and Closes: should be applicable here as well.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 4, 2025

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Jul 30, 2026
Patch available.
Web page

binder: fix use-after-free in binderfs_evict_inode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/aea61a1a77613d4184d7ebe7c1d7cb606458b43b
Web page

binder: fix use-after-free in binderfs_evict_inode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8c0a559825281764061a127632e5ad273f0466ad
Web page

binder: fix use-after-free in binderfs_evict_inode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/80ed8ab8efa0d18c03968a2321154f10e2d1a2e3

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-6.14 (6.14.0-1012.12) @ plucky2026-10-27ubuntu
ubuntulinux-tools-oem-6.14 (6.14.0-1012.12) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1012.12~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (6.14.0-1013.13~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-6.14 (6.14.0-1014.14) @ plucky2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-32.32~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (6.14.0-1016.17~24.04.1) @ noble2026-10-27ubuntu
linuxKernel @ 6.14.11 (fixes >=6.14.0)—osv

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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(7)

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 9× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 192 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 94 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-38176?
CVE-2025-38176 is a high-severity vulnerability; its CVE record was published on July 4, 2025. In the Linux kernel, the following vulnerability has been resolved: binder: fix use-after-free in binderfs_evict_inode() Running 'stress-ng --binderfs 16 --timeout 300' under KASAN-enabled kernel, I've noticed the following: BUG: KASAN: slab-use-after-free in binderfs_evict_inode+0x1de/0x2d0 Write…
When was the CVE record for CVE-2025-38176 published?
The CVE record for CVE-2025-38176 was published on July 4, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2025-38176 actively exploited?
CVE-2025-38176 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-38176?
CVE-2025-38176 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-38176?
A fix for CVE-2025-38176 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-38176

Explore →

Is Your Infrastructure Affected by CVE-2025-38176?

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

Book a Demo →Browse All CVEs