# CVE-2026-53160: misc: fastrpc: fix use-after-free race in fastrpc_map_create

> A use-after-free race condition in the Linux kernel's fastrpc driver allows attackers to execute arbitrary code or escalate privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2026-53160, DEBIAN-CVE-2026-53160, GHSA-4wgj-8vww-9v4h, ROOT-OS-DEBIAN-12-CVE-2026-53160, ROOT-OS-UBUNTU-2404-CVE-2026-53160, UBUNTU-CVE-2026-53160

## What is CVE-2026-53160?

CVE-2026-53160 is a high-severity use after free vulnerability in Linux kernel, published on 25 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

misc: fastrpc: fix use-after-free race in fastrpc_map_create

fastrpc_map_lookup returns a raw pointer after releasing fl->lock. The
caller fastrpc_map_create then calls fastrpc_map_get (kref_get_unless_zero)
on this unprotected pointer. A concurrent MEM_UNMAP can free the map
between the lock release and the kref operation, resulting in a
use-after-free on the freed slab object.

Restore the take_ref parameter to fastrpc_map_lookup so the reference
is acquired atomically under fl->lock before the pointer is exposed to
the caller.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2026-53160?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-53160?

Apply the vendor's patch.

## Is CVE-2026-53160 being exploited?

There is no known exploitation of CVE-2026-53160 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53160 and fix it if it is affected.

What it is: CVE-2026-53160 is a high-severity use after free vulnerability in Linux kernel, published on 25 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53160 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53160/ (Markdown: https://insights.sbomify.com/CVE-2026-53160/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53160
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53160
- OSV: https://osv.dev/vulnerability/CVE-2026-53160

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53160/
Summaries are generated and may contain mistakes; the official description above is the record.