CVE-2023-53320: scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info()
In the Linux kernel, the following vulnerability has been resolved:
scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info()
The function mpi3mr_get_all_tgt_info() has four issues:
1) It calculates valid entry length in alltgt_info assuming the header part
of the struct mpi3mr_device_map_info would equal to sizeof(u32). The
correct size is sizeof(u64).
2) When it calculates the valid entry length kern_entrylen, it excludes one
entry by subtracting 1 from num_devices.
3) It copies num_device by calling memcpy(). Substitution is enough.
4) It does not specify the calculated length to sg_copy_from_buffer().
Instead, it specifies the payload length which is larger than the
alltgt_info size. It causes "BUG: KASAN: slab-out-of-bounds".
Fix the issues by using the correct header size, removing the subtraction
from num_devices, replacing the memcpy() with substitution and specifying
the correct length to sg_copy_from_buffer().
Security readout for executives and security teams
Plain-English summary
CVE-2023-53320 is a Linux kernel memory safety flaw in the mpi3mr SCSI driver. A local user could potentially trigger out-of-bounds kernel memory access, risking system compromise or crash. It is high severity, but the provided sources do not show active exploitation.
Executive priority
Treat as a high-priority kernel patching item, especially for shared Linux infrastructure. Business urgency is driven by local privilege and kernel memory impact, not by evidence of active exploitation in the supplied sources.
Technical view
The flaw is in mpi3mr_get_all_tgt_info(). Incorrect entry-length calculations and an oversized sg_copy_from_buffer() length can cause a KASAN-reported slab out-of-bounds condition. The CVSS 3.1 vector is local, low-complexity, low-privilege, no user interaction, with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely on Linux systems running affected kernel builds where the mpi3mr SCSI driver is present and reachable by local users. The source data names Linux kernel versions and commits, but exact distribution-specific affected ranges require vendor validation.
Exploitation context
The provided CVE data rates exploitation as local with low privileges required. CISA KEV is false, and no cited source in the bundle states active exploitation or public weaponization.
Researcher notes
The root issue is CWE-787 out-of-bounds write/read risk from miscalculated device-map buffer sizing. Source evidence supports local attack requirements and high CIA impact, but does not provide a complete, distribution-ready affected-version matrix.
Mitigation direction
Apply Linux kernel updates containing the upstream stable fixes.
Use distribution vendor advisories to confirm fixed package versions.
Prioritize multi-user systems and hosts using mpi3mr-related storage paths.
Restrict unnecessary local shell access on exposed affected systems.
Track kernel update completion through normal patch governance.
Validation and detection
Inventory Linux kernel versions across affected server groups.
Determine whether the mpi3mr driver is present or loaded.
Map installed distro kernels against vendor fixed-version guidance.
Confirm patched kernels include one of the cited stable fixes.
Review local-user exposure on systems awaiting patching.
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.
cwe · low confidence lookup
CWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.