Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 24 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-36920, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df – < 5f0266044dc611563539705bff0b3e1545fbb6aa
    • affected c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df – < f09318244c6cafd10aca741b9c01e0a2c362d43a
    • affected c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df – < 4d2772324f43cf5674ac3dbe3f74a7e656396716
    • affected c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df – < 429846b4b6ce9853e0d803a2357bb2e55083adf0
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 6.1.91 – ≤ 6.1.*
    • unaffected 6.6.31 – ≤ 6.6.*
    • unaffected 6.8.10 – ≤ 6.8.*
    • unaffected 6.9 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-36920 badge
[![CVE-2024-36920](https://cveledger.app/badge/CVE-2024-36920.svg)](https://cveledger.app/cve/CVE-2024-36920)

Record last updated .