CVE & CISA-KEV Catalog

CVE-2025-38176

HIGH
7.8
CVSS v3
NVD

Description

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: <TASK> 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 </TASK> 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.

How to fix

Remediation Available
linux-aws-6.14Ubuntu
Fixed in:6.14.0-1013.13~24.04.1USN-7769-3
linux-gcp-6.14Ubuntu
Fixed in:6.14.0-1016.17~24.04.1USN-7769-1
linux-hwe-6.14Ubuntu
Fixed in:6.14.0-32.32~24.04.1USN-7769-3
linux-image-6.14.0-1012-oemUbuntu
Fixed in:6.14.0-1012.12USN-7771-1
linux-image-6.14.0-1012-realtimeUbuntu
Fixed in:6.14.0-1012.12~24.04.1USN-7769-2
linux-image-6.14.0-1013-awsUbuntu
Fixed in:6.14.0-1013.13~24.04.1USN-7769-3
linux-image-6.14.0-1013-aws-64kUbuntu
Fixed in:6.14.0-1013.13~24.04.1USN-7769-3
linux-image-6.14.0-1013-oracleUbuntu
Fixed in:6.14.0-1013.13~24.04.1USN-7789-1
linux-image-6.14.0-1013-oracle-64kUbuntu
Fixed in:6.14.0-1013.13~24.04.1USN-7789-1
linux-image-6.14.0-1016-gcpUbuntu
Fixed in:6.14.0-1016.17~24.04.1USN-7769-1
linux-image-6.14.0-1016-gcp-64kUbuntu
Fixed in:6.14.0-1016.17~24.04.1USN-7769-1
linux-image-6.14.0-32-genericUbuntu
Fixed in:6.14.0-32.32~24.04.1USN-7769-3
linux-image-6.14.0-32-generic-64kUbuntu
Fixed in:6.14.0-32.32~24.04.1USN-7769-3
linux-image-awsUbuntu
Fixed in:6.14.0-1013.13~24.04.1USN-7769-3
linux-image-aws-6.14Ubuntu
Fixed in:6.14.0-1013.13~24.04.1USN-7769-3
linux-image-aws-64kUbuntu
Fixed in:6.14.0-1013.13~24.04.1USN-7769-3
linux-image-aws-64k-6.14Ubuntu
Fixed in:6.14.0-1013.13~24.04.1USN-7769-3
linux-image-gcpUbuntu
Fixed in:6.14.0-1016.17~24.04.1USN-7769-1
linux-image-gcp-6.14Ubuntu
Fixed in:6.14.0-1016.17~24.04.1USN-7769-1
linux-image-gcp-64kUbuntu
Fixed in:6.14.0-1016.17~24.04.1USN-7769-1
linux-image-gcp-64k-6.14Ubuntu
Fixed in:6.14.0-1016.17~24.04.1USN-7769-1
linux-image-generic-6.14Ubuntu
Fixed in:6.14.0-32.32~24.04.1USN-7769-3
linux-image-generic-64k-6.14Ubuntu
Fixed in:6.14.0-32.32~24.04.1USN-7769-3
linux-image-generic-64k-hwe-24.04Ubuntu
Fixed in:6.14.0-32.32~24.04.1USN-7769-3
linux-image-generic-hwe-24.04Ubuntu
Fixed in:6.14.0-32.32~24.04.1USN-7769-3
linux-image-oem-24.04Ubuntu
Fixed in:6.14.0-1012.12USN-7771-1
linux-image-oem-24.04aUbuntu
Fixed in:6.14.0-1012.12USN-7771-1
linux-image-oem-24.04bUbuntu
Fixed in:6.14.0-1012.12USN-7771-1
linux-image-oem-24.04cUbuntu
Fixed in:6.14.0-1012.12USN-7771-1
linux-image-oem-6.14Ubuntu
Fixed in:6.14.0-1012.12USN-7771-1
linux-image-oracleUbuntu
Fixed in:6.14.0-1013.13~24.04.1USN-7789-1
linux-image-oracle-6.14Ubuntu
Fixed in:6.14.0-1013.13~24.04.1USN-7789-1
linux-image-oracle-64kUbuntu
Fixed in:6.14.0-1013.13~24.04.1USN-7789-1
linux-image-oracle-64k-6.14Ubuntu
Fixed in:6.14.0-1013.13~24.04.1USN-7789-1
linux-image-realtime-6.14Ubuntu
Fixed in:6.14.0-1012.12~24.04.1USN-7769-2
linux-image-realtime-hwe-24.04Ubuntu
Fixed in:6.14.0-1012.12~24.04.1USN-7769-2
linux-image-virtual-6.14Ubuntu
Fixed in:6.14.0-32.32~24.04.1USN-7769-3
linux-image-virtual-hwe-24.04Ubuntu
Fixed in:6.14.0-32.32~24.04.1USN-7769-3
linux-oem-6.14Ubuntu
Fixed in:6.14.0-1012.12USN-7771-1
linux-oracle-6.14Ubuntu
Fixed in:6.14.0-1013.13~24.04.1USN-7789-1
linux-realtime-6.14Ubuntu
Fixed in:6.14.0-1012.12~24.04.1USN-7769-2

Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.

CVSS v3 Vector

Exploitability

Attack VectorLocal
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploit Intelligence

0.14%probability of exploitation in 30 days
4thpercentile

Low risk: more likely to be exploited than 4% of all known CVEs.

References

Related Vulnerabilities

Other CWE-416 (Use After Free) vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2019-0708Critical9.8100%KEV + Ransom-
CVE-2021-31166Critical9.8100%KEVFix
CVE-2015-5119Critical9.899%KEV-
CVE-2010-3962High8.197%KEV-
CVE-2015-0313Critical9.896%KEVFix
CVE-2017-9798High7.595%-Fix
Embed a live status badge for CVE-2025-38176
CVE-2025-38176 severity badge

Markdown

[![CVE-2025-38176](https://tridentstack.com/cve/badge/CVE-2025-38176.svg)](https://tridentstack.com/cve/CVE-2025-38176)

HTML

<a href="https://tridentstack.com/cve/CVE-2025-38176"><img src="https://tridentstack.com/cve/badge/CVE-2025-38176.svg" alt="CVE-2025-38176"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

Start free

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2025-11-19.