# CVE-2023-54083: phy: tegra: xusb: Clear the driver reference in usb-phy dev

> A use-after-free vulnerability in the Linux kernel's Tegra XUSB PHY driver allows attackers to potentially execute code or cause a system crash.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 5 Aug 2026
- **Also known as:** BELL-CVE-2023-54083, DEBIAN-CVE-2023-54083, GHSA-mr7q-47cq-r2xm, UBUNTU-CVE-2023-54083

## What is CVE-2023-54083?

CVE-2023-54083 is a high-severity use after free 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:

phy: tegra: xusb: Clear the driver reference in usb-phy dev

For the dual-role port, it will assign the phy dev to usb-phy dev and
use the port dev driver as the dev driver of usb-phy.

When we try to destroy the port dev, it will destroy its dev driver
as well. But we did not remove the reference from usb-phy dev. This
might cause the use-after-free issue in KASAN.

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


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

Apply the vendor's patch.

## Is CVE-2023-54083 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-54083 is a high-severity use after free 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-54083 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-54083/ (Markdown: https://insights.sbomify.com/CVE-2023-54083/index.md)
```

## Sources

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

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