scsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue
The mpi3mr SCSI driver in Linux kernels 5.14.0 to before 6.6.160, 6.7.0 to before 6.12.24, 6.13.0 to before 6.13.12, and 6.14.0 to before 6.14.3 is affected. Fixed in those branches' later releases.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 6.6.160, 6.12.24, 6.13.12, 6.14.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.14
- KernelLinux
From 5.14.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.24; From 6.13.0 · fixed in 6.13.12; From 6.14.0 · fixed in 6.14.3
References 6
git.kernel.org
Questions about CVE-2025-37861
What does this mean?
The task management thread can access a reply queue ID that points to memory that is no longer allocated, because it runs at the same time as the reset thread that resets those queues. The result is a crash.Source: git.kernel.org
Am I affected, and how do I check?
The affected kernels are those in the listed ranges: 5.14.0 before 6.6.160, 6.7.0 before 6.12.24, 6.13.0 before 6.13.12, and 6.14.0 before 6.14.3. To check, run uname -r to see the kernel version and lsmod | grep mpi3mr to see whether the mpi3mr driver is loaded.Source: git.kernel.org
What should I do about it?
Update to a kernel with the fix: 6.6.160, 6.12.24, 6.13.12, or 6.14.3 for the matching branch, or any later release.Source: git.kernel.org
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data