# CVE-2023-54052: wifi: mt76: mt7921: fix skb leak by txs missing in AMSDU

> A missing transmission status in AMSDU frames causes socket buffer leaks, temporarily stopping network connectivity in the mt7921 Wi-Fi driver.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2023-54052, DEBIAN-CVE-2023-54052, GHSA-4jff-2mpg-6xjx, ROOT-OS-UBUNTU-2204-CVE-2023-54052, UBUNTU-CVE-2023-54052

## What is CVE-2023-54052?

CVE-2023-54052 is a denial of service vulnerability in Linux, published on 24 Dec 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:

wifi: mt76: mt7921: fix skb leak by txs missing in AMSDU

txs may be dropped if the frame is aggregated in AMSDU. When the problem
shows up, some SKBs would be hold in driver to cause network stopped
temporarily. Even if the problem can be recovered by txs timeout handling,
mt7921 still need to disable txs in AMSDU to avoid this issue.

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


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

Apply the vendor's patch.

## Is CVE-2023-54052 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-54052 is a denial of service vulnerability in Linux, published on 24 Dec 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-54052 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-54052/ (Markdown: https://insights.sbomify.com/CVE-2023-54052/index.md)
```

## Sources

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

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