Kernel memory corruption via FastRPC cleanup race
Published Jun 25, 2026 · Updated Jun 25, 2026
Use-after-free in the Linux kernel FastRPC driver allows local users to corrupt kernel memory by racing file closure with DSP cleanup. fastrpc_device_release() frees fastrpc_user while deferred fastrpc_context_free() work can still dereference it through buffer, map, or lock cleanup paths. Access to a FastRPC device and an in-flight DSP invocation are required; the stale dereference can crash the kernel or support kernel-memory corruption.
Summary
What happened
Use-after-free in the Linux kernel FastRPC driver allows local users to corrupt kernel memory by racing file closure with DSP cleanup. fastrpc_device_release() frees fastrpc_user while deferred fastrpc_context_free() work can still dereference it through buffer, map, or lock cleanup paths. Access to a FastRPC device and an in-flight DSP invocation are required; the stale dereference can crash the kernel or support kernel-memory corruption.
The record
- CVE
- CVE-2026-53161
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 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=5.1
- Affected versionversion=6cffd79504ce040f460831030d3069fa1c99bb71 <5278ccd357e0d7aeeb1e76c0f3e0e02894a9897c
- Affected versionversion=6cffd79504ce040f460831030d3069fa1c99bb71 <c6e5c2be09f814377d7f1ce97370a5b7b3e02814
- Affected versionversion=6cffd79504ce040f460831030d3069fa1c99bb71 <d42679eef34dd590b694ce3b666c5e2ba10cd4bf
- Affected versionversion=6cffd79504ce040f460831030d3069fa1c99bb71 <df08fadcf0e5f3708365ec3b6d30b5aafd98bea1
- Affected versionversion=6cffd79504ce040f460831030d3069fa1c99bb71 <e1e3a05efe5954d5bad01157d79429d39a67a7ae
- Affected versionversion=6cffd79504ce040f460831030d3069fa1c99bb71 <e85eb5feca8e254905ffa6c57a3c99c89a674a0f
- Affected versionversion=6cffd79504ce040f460831030d3069fa1c99bb71 <ecea4967c2bff92c2fafbc59893f711b39f7b152
- Affected versionversion=6cffd79504ce040f460831030d3069fa1c99bb71 <fbe0947420eec18a84638d29468c2d563ce4e6a3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Public exploit references
No public exploit references are available in this record.
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