LiveActive security incident?Get immediate response
CVE Record

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

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]

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel race condition in the legacy mptlan driver. During driver removal, background work can still access freed network-device memory, causing a use-after-free. The sources do not provide CVSS, confirmed impact, or exploitation evidence, so business urgency depends on whether affected kernels and this driver are present.

Executive priority

Treat as targeted patch hygiene unless your fleet uses this legacy driver or affected storage/network hardware. There is no exploitation evidence in the supplied sources, but kernel memory-safety issues still warrant inclusion in normal kernel update cycles.

Technical view

mptlan_probe() initializes priv->post_buckets_task, and mpt_lan_wake_post_buckets_task() can start work. During mptlan_remove(), free_netdev() may free dev while mpt_lan_post_receive_buckets_work() still reads dev->mtu. The kernel fix finishes the work before cleanup in mptlan_remove().

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the mptlan driver available and exercised, especially where driver unload or device removal occurs. The bundle lists multiple affected Linux kernel lines but does not identify distributions or package versions.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. It describes a race during driver unload, not a remote protocol flaw. Any practical exploitability, privilege requirement, or crash-only behavior is not established by the provided sources.

Researcher notes

The key evidence is the upstream race description and stable fixes. The record lacks CVSS, CWE, exploitability analysis, and distribution mapping. Avoid broad claims beyond a use-after-free in mptlan_remove() caused by unfinished workqueue activity.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes.
  • Prioritize systems where mptlan is built, loaded, or tied to supported hardware.
  • Check distribution advisories for exact fixed package versions.
  • If updates are unavailable, follow vendor guidance for reducing mptlan exposure.

Validation and detection

  • Inventory running Linux kernel versions against the affected versions listed in the CVE bundle.
  • Confirm whether the mptlan driver is present, loaded, or used on each host.
  • Verify installed kernel sources or packages include one of the referenced stable commits.
  • Review kernel logs for crashes around mptlan removal or device unload events.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-54310 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2unaffected
LinuxLinux2.6.12, 0, 4.14.316, 4.19.284, 5.4.244, 5.10.181, 5.15.113, 6.1.30, 6.3.4, 6.4affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.