Local kernel-memory corruption via unsynchronized binderfs deletion
Published Jul 4, 2025 · Updated Aug 5, 2026
Use-after-free in Linux kernel binderfs 6.14 through 6.15.1 allows local users to trigger an invalid kernel-memory write during deletion. binderfs_evict_inode removes a freed binder_device from the global binder_devices list without locking, so concurrent deletion corrupts the list. Local low-privileged access and concurrent binderfs device removal are required; the demonstrated consequence is a KASAN-detected invalid write.
Summary
What happened
Use-after-free in Linux kernel binderfs 6.14 through 6.15.1 allows local users to trigger an invalid kernel-memory write during deletion. binderfs_evict_inode removes a freed binder_device from the global binder_devices list without locking, so concurrent deletion corrupts the list. Local low-privileged access and concurrent binderfs device removal are required; the demonstrated consequence is a KASAN-detected invalid write.
The record
- CVE
- CVE-2025-38176
- Published
- Jul 4, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 4, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.14
- Affected versionversion=e77aff5528a183462714f750e45add6cc71e276a <80ed8ab8efa0d18c03968a2321154f10e2d1a2e3
- Affected versionversion=e77aff5528a183462714f750e45add6cc71e276a <8c0a559825281764061a127632e5ad273f0466ad
- Affected versionversion=e77aff5528a183462714f750e45add6cc71e276a <aea61a1a77613d4184d7ebe7c1d7cb606458b43b
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- stress-ng binderfs concurrency reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo