# CVE-2023-54093: media: anysee: fix null-ptr-deref in anysee_master_xfer

> A local attacker can cause a denial of service in the Linux kernel via a null pointer dereference in the Anysee media driver.

- **Severity:** Not scored
- **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:** 24 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2023-54093, DEBIAN-CVE-2023-54093, GHSA-4q89-7p83-q89w, UBUNTU-CVE-2023-54093

## What is CVE-2023-54093?

CVE-2023-54093 is a 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: anysee: fix null-ptr-deref in anysee_master_xfer

In anysee_master_xfer, msg is controlled by user. When msg[i].buf
is null and msg[i].len is zero, former checks on msg[i].buf would be
passed. Malicious data finally reach anysee_master_xfer. If accessing
msg[i].buf[0] without sanity check, null ptr deref would happen.
We add check on msg[i].len to prevent crash.

Similar commit:
commit 0ed554fd769a
("media: dvb-usb: az6027: fix null-ptr-deref in az6027_i2c_xfer()")

[hverkuil: add spaces around +]

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


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

Apply the vendor's patch.

## Is CVE-2023-54093 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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