# CVE-2023-52887: net: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new

> A flaw in the Linux kernel's J1939 CAN protocol allows attackers to cause a denial of service by sending tightly spaced RTS messages.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Jul 2024
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2023-52887, DEBIAN-CVE-2023-52887, GHSA-6fw4-4fx8-78rj, UBUNTU-CVE-2023-52887

## What is CVE-2023-52887?

CVE-2023-52887 is a high-severity denial of service vulnerability in Linux kernel, published on 29 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

net: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new

This patch enhances error handling in scenarios with RTS (Request to
Send) messages arriving closely. It replaces the less informative WARN_ON_ONCE
backtraces with a new error handling method. This provides clearer error
messages and allows for the early termination of problematic sessions.
Previously, sessions were only released at the end of j1939_xtp_rx_rts().

Potentially this could be reproduced with something like:
testj1939 -r vcan0:0x80 &
while true; do
	# send first RTS
	cansend vcan0 18EC8090#1014000303002301;
	# send second RTS
	cansend vcan0 18EC8090#1014000303002301;
	# send abort
	cansend vcan0 18EC8090#ff00000000002301;
done

Weakness: CWE-617 (Reachable Assertion)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2023-52887 being exploited?

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

What it is: CVE-2023-52887 is a high-severity denial of service vulnerability in Linux kernel, published on 29 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-52887 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-52887/ (Markdown: https://insights.sbomify.com/CVE-2023-52887/index.md)
```

## Sources

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

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