CVE-2025-38176
Description
A flaw was found in the Linux kernel's Android Binder filesystem (binderfs). A local user could trigger a use-after-free condition during concurrent device deletion operations due to improper synchronization. This flaw could allow an attacker to achieve arbitrary code execution or cause a Denial of Service (DoS) through kernel memory corruption.
Statement
Red Hat products are not impacted by this flaw, as the vulnerable Android binder filesystem code is absent from supported Red Hat Enterprise Linux kernels. In affected upstream environments, a local authenticated attacker could cause a denial of service or potentially execute arbitrary code through concurrent device deletion operations resulting in memory corruption. Because the underlying code was never introduced into Red Hat Enterprise Linux, no Red Hat distributions are exposed to this risk.
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.