# CVE-2023-54306: net: tls: avoid hanging tasks on the tx_lock

> An adversarial receiver can cause Linux kernel tasks to hang indefinitely by keeping the receive window at zero, leading to a denial of service.

- **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:** 30 Dec 2025
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2023-54306, DEBIAN-CVE-2023-54306, GHSA-f7xx-6pgx-v4hg, UBUNTU-CVE-2023-54306

## What is CVE-2023-54306?

CVE-2023-54306 is a high-severity denial of service vulnerability in Linux, published on 30 Dec 2025. 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: tls: avoid hanging tasks on the tx_lock

syzbot sent a hung task report and Eric explains that adversarial
receiver may keep RWIN at 0 for a long time, so we are not guaranteed
to make forward progress. Thread which took tx_lock and went to sleep
may not release tx_lock for hours. Use interruptible sleep where
possible and reschedule the work if it can't take the lock.

Testing: existing selftest passes

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


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

Apply the vendor's patch.

## Is CVE-2023-54306 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-54306 and fix it if it is affected.

What it is: CVE-2023-54306 is a high-severity denial of service vulnerability in Linux, published on 30 Dec 2025. 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-54306 in the wild and no public exploit code.

Affected product: Linux. 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-54306/ (Markdown: https://insights.sbomify.com/CVE-2023-54306/index.md)
```

## Sources

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

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