# CVE-2023-53218: rxrpc: Make it so that a waiting process can be aborted

> A flaw in the Linux kernel's rxrpc module allows a waiting process to hang indefinitely, causing a denial of service until patched.

- **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:** 15 Sep 2025
- **Updated:** 11 May 2026
- **Also known as:** AZL-71227, BELL-CVE-2023-53218, DEBIAN-CVE-2023-53218, GHSA-749j-m4j7-mhr2, ROOT-OS-DEBIAN-11-CVE-2023-53218, ROOT-OS-DEBIAN-12-CVE-2023-53218, ROOT-OS-UBUNTU-2204-CVE-2023-53218, UBUNTU-CVE-2023-53218

## What is CVE-2023-53218?

CVE-2023-53218 is a high-severity denial of service vulnerability in Linux kernel, published on 15 Sep 2025. 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:

rxrpc: Make it so that a waiting process can be aborted

When sendmsg() creates an rxrpc call, it queues it to wait for a connection
and channel to be assigned and then waits before it can start shovelling
data as the encrypted DATA packet content includes a summary of the
connection parameters.

However, sendmsg() may get interrupted before a connection gets assigned
and further sendmsg() calls will fail with EBUSY until an assignment is
made.

Fix this so that the call can at least be aborted without failing on
EBUSY.  We have to be careful here as sendmsg() mustn't be allowed to start
the call timer if the call doesn't yet have a connection assigned as an
oops may follow shortly thereafter.

## Which versions are affected by CVE-2023-53218?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2023-53218?

Apply the vendor's patch.

## Is CVE-2023-53218 being exploited?

There is no known exploitation of CVE-2023-53218 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-2023-53218 and fix it if it is affected.

What it is: CVE-2023-53218 is a high-severity denial of service vulnerability in Linux kernel, published on 15 Sep 2025. 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-2023-53218 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-2023-53218/ (Markdown: https://insights.sbomify.com/CVE-2023-53218/index.md)
```

## Sources

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

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