# CVE-2025-37861: scsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue

> A race condition in the mpi3mr driver causes a kernel crash when reset and task management threads access reply queues concurrently.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 May 2025
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-62498, AZL-70144, BELL-CVE-2025-37861, DEBIAN-CVE-2025-37861, GHSA-76hw-gx4c-xc29, RHSA-2026:3692, ROOT-OS-DEBIAN-12-CVE-2025-37861, ROOT-OS-UBUNTU-2204-CVE-2025-37861, ROOT-OS-UBUNTU-2404-CVE-2025-37861, UBUNTU-CVE-2025-37861

## What is CVE-2025-37861?

CVE-2025-37861 is a high-severity use after free vulnerability in Linux kernel, published on 9 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2025-37861?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bpftool-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:7.3.0-427.113.1.el9_4 |
| `kernel-64k-debug-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-64k-debug-devel` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-64k-debug-devel-matched` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-64k-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-64k-devel` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-64k-devel-matched` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-debug-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-debug-devel` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-debug-devel-matched` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-debuginfo-common-aarch64` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-debuginfo-common-ppc64le` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-debuginfo-common-s390x` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-debuginfo-common-x86_64` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-devel` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-devel-matched` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-doc` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-rt-debug-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-rt-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-tools-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-zfcpdump-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-zfcpdump-devel` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-zfcpdump-devel-matched` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `libperf-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `perf` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `perf-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `python3-perf-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `rtla` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `rv` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:5.14.0-427.113.1.el9_4 |
| `bpftool` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:7.3.0-427.113.1.el9_4 |
| `bpftool-debuginfo` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:7.3.0-427.113.1.el9_4 |
| `kernel` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-64k` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-64k-core` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-64k-debug` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-64k-debug-core` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-64k-debug-debuginfo` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-64k-debug-modules` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:5.14.0-427.113.1.el9_4 |
| `kernel-64k-debug-modules-core` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:5.14.0-427.113.1.el9_4 |

Products: Linux kernel.

## How do I fix CVE-2025-37861?

Apply the vendor's patch.

## Is CVE-2025-37861 being exploited?

There is no known exploitation of CVE-2025-37861 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-37861 and fix it if it is affected.

What it is: CVE-2025-37861 is a high-severity use after free vulnerability in Linux kernel, published on 9 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-37861 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-37861/ (Markdown: https://insights.sbomify.com/CVE-2025-37861/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-37861
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-37861
- OSV: https://osv.dev/vulnerability/CVE-2025-37861

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-37861/
Summaries are generated and may contain mistakes; the official description above is the record.