CVE-2025-38175: binder: fix yet another UAF in binder_devices
In the Linux kernel, the following vulnerability has been resolved:
binder: fix yet another UAF in binder_devices
Commit e77aff5528a18 ("binderfs: fix use-after-free in binder_devices")
addressed a use-after-free where devices could be released without first
being removed from the binder_devices list. However, there is a similar
path in binder_free_proc() that was missed:
==================================================================
BUG: KASAN: slab-use-after-free in binder_remove_device+0xd4/0x100
Write of size 8 at addr ffff0000c773b900 by task umount/467
CPU: 12 UID: 0 PID: 467 Comm: umount Not tainted 6.15.0-rc7-00138-g57483a362741 #9 PREEMPT
Hardware name: linux,dummy-virt (DT)
Call trace:
binder_remove_device+0xd4/0x100
binderfs_evict_inode+0x230/0x2f0
evict+0x25c/0x5dc
iput+0x304/0x480
dentry_unlink_inode+0x208/0x46c
__dentry_kill+0x154/0x530
[...]
Allocated by task 463:
__kmalloc_cache_noprof+0x13c/0x324
binderfs_binder_device_create.isra.0+0x138/0xa60
binder_ctl_ioctl+0x1ac/0x230
[...]
Freed by task 215:
kfree+0x184/0x31c
binder_proc_dec_tmpref+0x33c/0x4ac
binder_deferred_func+0xc10/0x1108
process_one_work+0x520/0xba4
[...]
==================================================================
Call binder_remove_device() within binder_free_proc() to ensure the
device is removed from the binder_devices list before being kfreed.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux Binder device cleanup can leave a freed object referenced in a device list. A later cleanup operation may access that memory, potentially crashing the system or enabling local compromise. The supplied CVSS score is 7.8, reflecting possible confidentiality, integrity, and availability impact.
Executive priority
Treat this as a high-priority local privilege and stability risk, especially on shared or exposed hosts. It is less urgent than an unauthenticated remote flaw, but the potential impact is complete compromise. Accelerate vendor-supported kernel updates while validating actual exposure.
Technical view
CVE-2025-38175 is a slab use-after-free in Linux Binder/binderfs cleanup. binder_free_proc() could free a device without removing it from binder_devices, allowing binder_remove_device() to access freed memory during inode eviction. The correction removes the device from the list before freeing it.
Likely exposure
Exposure is limited to affected Linux kernels where the relevant Binder/binderfs lifecycle is reachable. The CVSS vector requires local access and low privileges, with no user interaction. The supplied version data is ambiguous, so distribution-specific kernel builds must be checked against vendor guidance and the referenced fixes.
Exploitation context
The supplied record is not in CISA KEV, and no provided source confirms active exploitation or a public exploit. A KASAN trace demonstrates the memory-safety failure during device cleanup and unmounting, but it does not establish reliable code execution or exploitation in production.
Researcher notes
The reported failure is an eight-byte write to freed slab memory from binder_remove_device() during binderfs inode eviction. Allocation occurs during Binder device creation; freeing occurs through deferred Binder process cleanup. Exploitability beyond denial of service is not established by the supplied evidence, despite the CVSS impact assumptions.
Mitigation direction
Update to a vendor-supported kernel containing the applicable referenced fix.
Check distribution advisories because the supplied affected-version mapping is ambiguous.
Prioritize systems where untrusted local users can reach Binder or binderfs functionality.
If patching is delayed, seek vendor guidance; no source-backed workaround is provided.
Validation and detection
Inventory deployed kernel builds and identify systems using affected Linux branches.
Map distribution package versions to the three referenced stable-kernel commits.
Confirm the selected kernel package includes binder_free_proc() device-list removal.
After updating, verify systems boot and report the intended patched kernel build.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38175 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.