LiveActive security incident?Get immediate response
CVE Record

CVE-2024-36920: scsi: mpi3mr: Avoid memcpy field-spanning write WARNING

In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Avoid memcpy field-spanning write WARNING When the "storcli2 show" command is executed for eHBA-9600, mpi3mr driver prints this WARNING message: memcpy: detected field-spanning write (size 128) of single field "bsg_reply_buf->reply_buf" at drivers/scsi/mpi3mr/mpi3mr_app.c:1658 (size 1) WARNING: CPU: 0 PID: 12760 at drivers/scsi/mpi3mr/mpi3mr_app.c:1658 mpi3mr_bsg_request+0x6b12/0x7f10 [mpi3mr] The cause of the WARN is 128 bytes memcpy to the 1 byte size array "__u8 replay_buf[1]" in the struct mpi3mr_bsg_in_reply_buf. The array is intended to be a flexible length array, so the WARN is a false positive. To suppress the WARN, remove the constant number '1' from the array declaration and clarify that it has flexible length. Also, adjust the memory allocation size to match the change.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is tied to a warning in the mpi3mr SCSI driver when a storage management query is run against eHBA-9600 hardware. The source describes the warning as a false positive around a flexible-length reply buffer, not confirmed memory corruption. Business urgency is low unless affected storage hosts show driver warnings or stability concerns.

Executive priority

Handle during normal kernel maintenance unless storage hosts are logging warnings or affected hardware is business-critical. There is no cited active exploitation or CVSS score in the bundle, but affected storage infrastructure should still be patched through standard change control.

Technical view

The mpi3mr driver copied 128 bytes into a struct member declared as a one-byte array intended to behave as flexible length. Fortified memcpy detected this as a field-spanning write and emitted a WARN. The fix changes the array declaration to flexible length and adjusts allocation sizing.

Likely exposure

Exposure appears limited to Linux systems using the mpi3mr SCSI driver, especially Broadcom/LSI eHBA-9600-class storage environments where storcli2-style management operations are used. The bundle's version data is incomplete, so validate exposure against kernel package advisories and the referenced stable commits.

Exploitation context

The sources do not report active exploitation, public exploit use, KEV listing, privilege escalation, or remote attackability. The described trigger is an administrative storage query that causes a kernel warning. Treat exploitation evidence as absent, not disproven.

Researcher notes

The CVE appears to address a fortified memcpy warning caused by a one-byte placeholder array used as a flexible buffer. The source explicitly calls the warning a false positive. Evidence does not establish direct exploitability, impact beyond WARN logging, or downstream distribution fix status.

Mitigation direction

  • Check your Linux distribution's advisory for CVE-2024-36920.
  • Update affected kernels to builds containing the referenced stable fixes.
  • Prioritize storage hosts using the mpi3mr driver and eHBA-9600 hardware.
  • Monitor kernel logs for repeated mpi3mr WARN events.
  • Avoid inventing workarounds; follow vendor kernel guidance.

Validation and detection

  • Inventory Linux hosts with the mpi3mr driver loaded.
  • Identify systems using eHBA-9600 or related mpi3mr-supported adapters.
  • Compare installed kernel versions against distribution CVE status.
  • Review kernel logs for mpi3mr field-spanning memcpy warnings.
  • Confirm patched kernels include one of the referenced stable commits.
Prepared
Confidence
medium
Sources
6

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-2024-36920 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
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df, c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df, c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df, c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974dfunaffected
LinuxLinux5.14, 0, 6.1.91, 6.6.31, 6.8.10, 6.9affected
Weakness

CWE details

No CWE listed

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