CVE-2025-37861
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-416 · Use after free
- Record status
- Modified
Affected
- Linux Kernel < 6.12.24
- Linux Kernel < 6.13.12
- Linux Kernel < 6.14.3
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-37861.md and follow it. Check whether this project is affected by CVE-2025-37861. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/65ba18c84dbd03afe9b38c06c151239d97a09834
- https://git.kernel.org/stable/c/75b67dca4195e11ccf966a704787b2aa2754a457
- https://git.kernel.org/stable/c/8d310d66e2b0f5f9f709764641647e8a3a4924fa
- https://git.kernel.org/stable/c/f195fc060c738d303a21fae146dbf85e1595fb4c
References
- https://git.kernel.org/stable/c/31dad8d385953a886e57df70ab43ee25ba37797c
- https://git.kernel.org/stable/c/65ba18c84dbd03afe9b38c06c151239d97a09834
- https://git.kernel.org/stable/c/75b67dca4195e11ccf966a704787b2aa2754a457
- https://git.kernel.org/stable/c/8d310d66e2b0f5f9f709764641647e8a3a4924fa
- https://git.kernel.org/stable/c/e9efbd037b9002ce9dd012da612e857e98dfcb3e
- https://git.kernel.org/stable/c/f195fc060c738d303a21fae146dbf85e1595fb4c