# CVE-2023-54310: scsi: message: mptlan: Fix use after free bug in mptlan_remove() due to race condition

> A race condition in the mptlan driver causes a use-after-free during device removal, potentially allowing local attackers to execute code or crash the system.

- **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:** 30 Dec 2025
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2023-54310, DEBIAN-CVE-2023-54310, GHSA-52c3-vccj-p4f5, UBUNTU-CVE-2023-54310

## What is CVE-2023-54310?

CVE-2023-54310 is a high-severity use after free vulnerability in Linux, published on 30 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:

scsi: message: mptlan: Fix use after free bug in mptlan_remove() due to race condition

mptlan_probe() calls mpt_register_lan_device() which initializes the
&priv->post_buckets_task workqueue. A call to
mpt_lan_wake_post_buckets_task() will subsequently start the work.

During driver unload in mptlan_remove() the following race may occur:

CPU0                  CPU1

                    |mpt_lan_post_receive_buckets_work()
mptlan_remove()     |
  free_netdev()     |
    kfree(dev);     |
                    |
                    | dev->mtu
                    |   //use

Fix this by finishing the work prior to cleaning up in mptlan_remove().

[mkp: we really should remove mptlan instead of attempting to fix it]

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


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

Apply the vendor's patch.

## Is CVE-2023-54310 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-54310 is a high-severity use after free vulnerability in Linux, published on 30 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-54310 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-54310/ (Markdown: https://insights.sbomify.com/CVE-2023-54310/index.md)
```

## Sources

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

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