Vulnerability-Lookup

GHSA-6FX2-6QWR-35W9

Vulnerability from github – Published: 2025-12-30 15:30 – Updated: 2026-08-04 12:34

Details

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.

Severity

7.8 (High)


                  
                    CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2023-54234"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-12-30T13:16:11Z",
    "severity": "HIGH"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: mpi3mr: Fix missing mrioc-\u003eevtack_cmds initialization\n\nCommit c1af985d27da (\"scsi: mpi3mr: Add Event acknowledgment logic\")\nintroduced an array mrioc-\u003eevtack_cmds but initialization of the array\nelements was missed. They are just zero cleared. The function\nmpi3mr_complete_evt_ack() refers host_tag field of the elements. Due to the\nzero value of the host_tag field, the function calls clear_bit() for\nmrico-\u003eevtack_cmds_bitmap with wrong bit index. This results in memory\naccess to invalid address and \"BUG: KASAN: use-after-free\". This BUG was\nobserved at eHBA-9600 firmware update to version 8.3.1.0. To fix it, add\nthe missing initialization of mrioc-\u003eevtack_cmds.",
  "id": "GHSA-6fx2-6qwr-35w9",
  "modified": "2026-08-04T12:34:49Z",
  "published": "2025-12-30T15:30:32Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-54234"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/4e0dfdb48a824deac3dfbc67fb856ef2aee13529"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/67989091e11a974003ddf2ec39bc613df8eadd83"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/e39ea831ebad4ab15c4748cb62a397a8abcca36e"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2023-54234 (GCVE-0-2023-54234)

Vulnerability from cvelistv5 – Published: 2025-12-30 12:11 – Updated: 2026-08-05 09:18

Title

scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization

Summary

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.

Severity

7.8 (High)


                        
                          CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Assigner

Linux mitre root

References

3 references

URL	Tags
https://git.kernel.org/stable/c/4e0dfdb48a824deac…
https://git.kernel.org/stable/c/67989091e11a97400…
https://git.kernel.org/stable/c/e39ea831ebad4ab15…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: c1af985d27da2d530c22604644e9025810f57d7c , < 4e0dfdb48a824deac3dfbc67fb856ef2aee13529 (git) Affected: c1af985d27da2d530c22604644e9025810f57d7c , < 67989091e11a974003ddf2ec39bc613df8eadd83 (git) Affected: c1af985d27da2d530c22604644e9025810f57d7c , < e39ea831ebad4ab15c4748cb62a397a8abcca36e (git)
Linux	Linux	Affected: 5.17 Unaffected: 0 , < 5.17 (semver) Unaffected: 6.1.16 , ≤ 6.1.* (semver) Unaffected: 6.2.3 , ≤ 6.2.* (semver) Unaffected: 6.3 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/scsi/mpi3mr/mpi3mr_os.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "4e0dfdb48a824deac3dfbc67fb856ef2aee13529",
              "status": "affected",
              "version": "c1af985d27da2d530c22604644e9025810f57d7c",
              "versionType": "git"
            },
            {
              "lessThan": "67989091e11a974003ddf2ec39bc613df8eadd83",
              "status": "affected",
              "version": "c1af985d27da2d530c22604644e9025810f57d7c",
              "versionType": "git"
            },
            {
              "lessThan": "e39ea831ebad4ab15c4748cb62a397a8abcca36e",
              "status": "affected",
              "version": "c1af985d27da2d530c22604644e9025810f57d7c",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/scsi/mpi3mr/mpi3mr_os.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.17"
            },
            {
              "lessThan": "5.17",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.16",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.2.*",
              "status": "unaffected",
              "version": "6.2.3",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.16",
                  "versionStartIncluding": "5.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.2.3",
                  "versionStartIncluding": "5.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.3",
                  "versionStartIncluding": "5.17",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: mpi3mr: Fix missing mrioc-\u003eevtack_cmds initialization\n\nCommit c1af985d27da (\"scsi: mpi3mr: Add Event acknowledgment logic\")\nintroduced an array mrioc-\u003eevtack_cmds but initialization of the array\nelements was missed. They are just zero cleared. The function\nmpi3mr_complete_evt_ack() refers host_tag field of the elements. Due to the\nzero value of the host_tag field, the function calls clear_bit() for\nmrico-\u003eevtack_cmds_bitmap with wrong bit index. This results in memory\naccess to invalid address and \"BUG: KASAN: use-after-free\". This BUG was\nobserved at eHBA-9600 firmware update to version 8.3.1.0. To fix it, add\nthe missing initialization of mrioc-\u003eevtack_cmds."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The vulnerability is in a Broadcom MPI3 SAS/NVMe HBA driver and is reached through local controller reset/error-recovery paths and the local BSG management interface; there is no network-facing protocol handler involved.\nAC:L - Once a PREPARE_FOR_RESET event with ACK_REQUIRED has left evtack_cmds[0] permanently PENDING, the very next controller reset deterministically executes clear_bit() at fixed index 65512, with no race to win and no memory-layout precondition; the reporter reproduced it reliably on firmware update.\nPR:L - An unprivileged local user with ordinary I/O access to storage behind the HBA can drive the controller into the timeout/fault reset paths (MPI3MR_RESET_FROM_FIRMWARE, mpi3mr_fw.c:2468-2513) that call mpi3mr_flush_drv_cmds(); no capability check guards those escalation paths, so real root is not required.\nUI:N - The corrupting code runs entirely inside driver reset handling and the admin reply/interrupt path; no victim action such as mounting a filesystem or opening a file is needed.\nS:U - The out-of-bounds write corrupts kernel slab memory within the same kernel security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - A wild out-of-bounds bit write 8184 bytes past an 8-byte allocation corrupts an unrelated kernel object; clearing a bit in adjacent slab state (flags, length fields, pointer bits) can be groomed into an information-disclosure primitive, and KASAN classified the access as use-after-free.\nI:H - clear_bit() performs a read-modify-write far outside the bitmap allocation, giving an out-of-bounds write into arbitrary neighbouring slab memory \u2014 per guidance an OOB write is High, and with heap grooming the corrupted victim object can yield control over kernel data.\nA:H - The out-of-bounds write silently corrupts an unrelated freed/live slab object, producing the observed KASAN use-after-free splat and leading to kernel oops or panic during controller reset."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T09:18:14.409Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/4e0dfdb48a824deac3dfbc67fb856ef2aee13529"
        },
        {
          "url": "https://git.kernel.org/stable/c/67989091e11a974003ddf2ec39bc613df8eadd83"
        },
        {
          "url": "https://git.kernel.org/stable/c/e39ea831ebad4ab15c4748cb62a397a8abcca36e"
        }
      ],
      "title": "scsi: mpi3mr: Fix missing mrioc-\u003eevtack_cmds initialization",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2023-54234",
    "datePublished": "2025-12-30T12:11:25.021Z",
    "dateReserved": "2025-12-30T12:06:44.507Z",
    "dateUpdated": "2026-08-05T09:18:14.409Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.

Action not permitted

GHSA-6FX2-6QWR-35W9

CVE-2023-54234 (GCVE-0-2023-54234)

Tags

Sightings

Nomenclature