# CVE-2023-54143: media: mediatek: vcodec: fix resource leaks in vdec_msg_queue_init()

> A resource leak in the MediaTek video codec driver can lead to memory exhaustion and denial of service, requiring kernel patching.

- **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-54143, DEBIAN-CVE-2023-54143, GHSA-rh3v-jp2c-rq2q, UBUNTU-CVE-2023-54143

## What is CVE-2023-54143?

CVE-2023-54143 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:

media: mediatek: vcodec: fix resource leaks in vdec_msg_queue_init()

If we encounter any error in the vdec_msg_queue_init() then we need
to set "msg_queue->wdma_addr.size = 0;".  Normally, this is done
inside the vdec_msg_queue_deinit() function.  However, if the
first call to allocate &msg_queue->wdma_addr fails, then the
vdec_msg_queue_deinit() function is a no-op.  For that situation, just
set the size to zero explicitly and return.

There were two other error paths which did not clean up before returning.
Change those error paths to goto mem_alloc_err.

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


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

Apply the vendor's patch.

## Is CVE-2023-54143 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-54143 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-54143 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-54143/ (Markdown: https://insights.sbomify.com/CVE-2023-54143/index.md)
```

## Sources

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

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