LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54234: scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization

In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization Commit c1af985d27da ("scsi: mpi3mr: Add Event acknowledgment logic") introduced an array mrioc->evtack_cmds but initialization of the array elements was missed. They are just zero cleared. The function mpi3mr_complete_evt_ack() refers host_tag field of the elements. Due to the zero value of the host_tag field, the function calls clear_bit() for mrico->evtack_cmds_bitmap with wrong bit index. This results in memory access to invalid address and "BUG: KASAN: use-after-free". This BUG was observed at eHBA-9600 firmware update to version 8.3.1.0. To fix it, add the missing initialization of mrioc->evtack_cmds.

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

Security readout for executives and security teams

Plain-English summary

CVE-2023-54234 is a Linux kernel storage-driver bug in mpi3mr. A missing initialization can make the kernel access an invalid memory address, causing a crash condition. The public record notes it was observed during an eHBA-9600 firmware update. No public source provided here indicates active exploitation.

Executive priority

Treat as a targeted infrastructure stability issue, not a broad internet-facing emergency. Prioritize storage-heavy Linux servers, especially where firmware maintenance is planned. Business impact is most likely unplanned downtime or maintenance disruption if affected systems hit the kernel bug.

Technical view

The mpi3mr event-acknowledgment logic added mrioc->evtack_cmds but did not initialize array elements. mpi3mr_complete_evt_ack() reads a zeroed host_tag and clears the wrong bitmap index, leading to invalid memory access and a KASAN use-after-free report. Stable kernel commits add the missing initialization.

Likely exposure

Most relevant to Linux systems using the mpi3mr SCSI driver and affected kernel builds. Exposure is likely narrower than general Linux exposure because the described failure path involves specific storage-driver event acknowledgment behavior. The provided affected-version data is limited; validate against vendor kernel packaging.

Exploitation context

The source bundle reports a kernel BUG observed during eHBA-9600 firmware update to firmware 8.3.1.0. It does not describe remote exploitation, privilege escalation, or confirmed in-the-wild exploitation. KEV status is false in the provided data.

Researcher notes

Severity and CVSS are not provided in the source bundle. The affected-version metadata appears incomplete for direct fleet mapping. The strongest evidence is the kernel commit narrative and stable fix references. Avoid claiming exploitability beyond crash/invalid memory access unless additional sources support it.

Mitigation direction

  • Update to a Linux kernel containing the referenced stable mpi3mr initialization fix.
  • Check your Linux distribution or appliance vendor advisory for packaged kernel fixes.
  • Prioritize systems using mpi3mr-supported storage controllers or planning firmware updates.
  • If patching is delayed, monitor vendor guidance for operational workarounds.

Validation and detection

  • Inventory Linux systems using the mpi3mr driver or affected storage hardware.
  • Confirm running kernel packages include one of the referenced stable fixes.
  • Review kernel logs for KASAN, BUG, use-after-free, or mpi3mr event-acknowledgment errors.
  • Validate distribution backport status rather than relying only on upstream version numbers.
Prepared
Confidence
medium
Sources
5

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-54234 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
4Source 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
LinuxLinuxc1af985d27da2d530c22604644e9025810f57d7c, c1af985d27da2d530c22604644e9025810f57d7c, c1af985d27da2d530c22604644e9025810f57d7cunaffected
LinuxLinux5.17, 0, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

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