CVE-2025-37861 (GCVE-0-2025-37861)
Vulnerability from cvelistv5
Published
2025-05-09 06:42
Modified
2026-08-05 11:57
Severity ?
7.8 (High) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Summary
In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue When the task management thread processes reply queues while the reset thread resets them, the task management thread accesses an invalid queue ID (0xFFFF), set by the reset thread, which points to unallocated memory, causing a crash. Add flag 'io_admin_reset_sync' to synchronize access between the reset, I/O, and admin threads. Before a reset, the reset handler sets this flag to block I/O and admin processing threads. If any thread bypasses the initial check, the reset thread waits up to 10 seconds for processing to finish. If the wait exceeds 10 seconds, the controller is marked as unrecoverable.
References
Impacted products
Vendor Product Version
Linux Linux Version: c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df
Version: c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df
Version: c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df
Version: c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/scsi/mpi3mr/mpi3mr.h",
            "drivers/scsi/mpi3mr/mpi3mr_fw.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "65ba18c84dbd03afe9b38c06c151239d97a09834",
              "status": "affected",
              "version": "c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df",
              "versionType": "git"
            },
            {
              "lessThan": "8d310d66e2b0f5f9f709764641647e8a3a4924fa",
              "status": "affected",
              "version": "c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df",
              "versionType": "git"
            },
            {
              "lessThan": "75b67dca4195e11ccf966a704787b2aa2754a457",
              "status": "affected",
              "version": "c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df",
              "versionType": "git"
            },
            {
              "lessThan": "f195fc060c738d303a21fae146dbf85e1595fb4c",
              "status": "affected",
              "version": "c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/scsi/mpi3mr/mpi3mr.h",
            "drivers/scsi/mpi3mr/mpi3mr_fw.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.14"
            },
            {
              "lessThan": "5.14",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.24",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.13.*",
              "status": "unaffected",
              "version": "6.13.12",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.14.*",
              "status": "unaffected",
              "version": "6.14.3",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.15",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.24",
                  "versionStartIncluding": "5.14",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.13.12",
                  "versionStartIncluding": "5.14",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.14.3",
                  "versionStartIncluding": "5.14",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.15",
                  "versionStartIncluding": "5.14",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue\n\nWhen the task management thread processes reply queues while the reset\nthread resets them, the task management thread accesses an invalid queue ID\n(0xFFFF), set by the reset thread, which points to unallocated memory,\ncausing a crash.\n\nAdd flag \u0027io_admin_reset_sync\u0027 to synchronize access between the reset,\nI/O, and admin threads. Before a reset, the reset handler sets this flag to\nblock I/O and admin processing threads. If any thread bypasses the initial\ncheck, the reset thread waits up to 10 seconds for processing to finish. If\nthe wait exceeds 10 seconds, the controller is marked as unrecoverable."
        }
      ],
      "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 vulnerable code is a Broadcom MPI3 SAS/NVMe HBA driver path reached only through local I/O submission, SCSI error handling, or the /dev/bsg management node; there is no remote or adjacent-network reachability.\nAC:L - The attacker controls both sides of the race \u2014 sustained I/O to a device on the controller keeps threads inside mpi3mr_process_op_reply_q() (threaded IRQ poll, blk-mq poll, or SCSI-EH task-management polling), while the same load storm drives the timeout/EH escalation and reset paths that call mpi3mr_memset_buffers(); the window can be retried indefinitely with no attacker-uncontrollable precondition.\nPR:L - An unprivileged local user with access to any block device backed by the mpi3mr HBA can drive the polling side and induce the timeout-driven error-recovery side; the higher-privileged BSG reset path (CAP_SYS_RAWIO) only makes triggering more deterministic and is not required.\nUI:N - The race is triggered entirely by the attacker\u0027s own I/O and error-recovery activity; no action by another user or administrator is needed.\nS:U - The corruption is confined to the kernel\u0027s own memory and MMIO mappings within the same security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - The zeroed num_replies makes reply_ci grow without wrapping, so mpi3mr_get_reply_desc() reads segment pointers past the q_segments array and dereferences them, giving unbounded out-of-bounds kernel reads whose contents flow into reply/sense processing and can reach userspace.\nI:H - With qid/request_queue_id zeroed, WRITE_ONCE(mrioc-\u003ereq_qinfo[0xFFFF].ci, ...) performs an out-of-bounds write roughly 4.5 MB beyond the allocation into unrelated kernel heap, and writel() targets addresses ~512 KB outside the ioremap()ed BAR \u2014 memory corruption usable to build a write primitive.\nA:H - The commit explicitly states the invalid 0xFFFF queue ID points to unallocated memory and causes a crash; the writel() to oper_queue_indexes[0xFFFF] hits an unmapped kernel virtual address, producing a kernel oops and loss of the storage controller."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:57:53.888Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/65ba18c84dbd03afe9b38c06c151239d97a09834"
        },
        {
          "url": "https://git.kernel.org/stable/c/8d310d66e2b0f5f9f709764641647e8a3a4924fa"
        },
        {
          "url": "https://git.kernel.org/stable/c/75b67dca4195e11ccf966a704787b2aa2754a457"
        },
        {
          "url": "https://git.kernel.org/stable/c/f195fc060c738d303a21fae146dbf85e1595fb4c"
        }
      ],
      "title": "scsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-37861",
    "datePublished": "2025-05-09T06:42:07.245Z",
    "dateReserved": "2025-04-16T04:51:23.957Z",
    "dateUpdated": "2026-08-05T11:57:53.888Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.