Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 18 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-37861, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.33% · top 74% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df – < e9efbd037b9002ce9dd012da612e857e98dfcb3e
    • affected c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df – < 31dad8d385953a886e57df70ab43ee25ba37797c
    • affected c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df – < 65ba18c84dbd03afe9b38c06c151239d97a09834
    • affected c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df – < 8d310d66e2b0f5f9f709764641647e8a3a4924fa
    • affected c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df – < 75b67dca4195e11ccf966a704787b2aa2754a457
    • affected c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df – < f195fc060c738d303a21fae146dbf85e1595fb4c
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.24 – ≤ 6.12.*
    • unaffected 6.13.12 – ≤ 6.13.*
    • unaffected 6.14.3 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-37861 badge
[![CVE-2025-37861](https://cveledger.app/badge/CVE-2025-37861.svg)](https://cveledger.app/cve/CVE-2025-37861)

Record last updated .