CVE-2025-21723: scsi: mpi3mr: Fix possible crash when setting up bsg fails
In the Linux kernel, the following vulnerability has been resolved:
scsi: mpi3mr: Fix possible crash when setting up bsg fails
If bsg_setup_queue() fails, the bsg_queue is assigned a non-NULL value.
Consequently, in mpi3mr_bsg_exit(), the condition "if(!mrioc->bsg_queue)"
will not be satisfied, preventing execution from entering
bsg_remove_queue(), which could lead to the following crash:
BUG: kernel NULL pointer dereference, address: 000000000000041c
Call Trace:
<TASK>
mpi3mr_bsg_exit+0x1f/0x50 [mpi3mr]
mpi3mr_remove+0x6f/0x340 [mpi3mr]
pci_device_remove+0x3f/0xb0
device_release_driver_internal+0x19d/0x220
unbind_store+0xa4/0xb0
kernfs_fop_write_iter+0x11f/0x200
vfs_write+0x1fc/0x3e0
ksys_write+0x67/0xe0
do_syscall_64+0x38/0x80
entry_SYSCALL_64_after_hwframe+0x78/0xe2
Security readout for executives and security teams
Plain-English summary
CVE-2025-21723 is a Linux kernel availability flaw in the mpi3mr SCSI driver. Under a bsg setup failure and later device removal path, the kernel can hit a NULL pointer dereference and crash. The impact is service interruption, not data theft or tampering, based on the provided CVSS vector.
Executive priority
Treat this as a moderate operational resilience issue. It is unlikely to drive emergency response without active exploitation evidence, but systems relying on impacted storage drivers should be patched in normal kernel maintenance windows to reduce crash risk.
Technical view
The flaw is CWE-476 in Linux mpi3mr cleanup logic. If bsg_setup_queue() fails, bsg_queue can remain non-NULL, causing mpi3mr_bsg_exit() to skip the intended removal path and dereference invalid state during driver removal or unbind. CVSS is 5.5: local attack vector, low complexity, low privileges, no user interaction, high availability impact.
Likely exposure
Exposure is limited to Linux systems using the mpi3mr SCSI driver and kernel versions matching the vendor's affected ranges. The source bundle lists Linux kernel affected version markers including 5.19, 6.12.13, 6.13.2, and 6.14, but distribution backport status must be verified with each kernel vendor.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The described failure is local and availability-focused. Evidence supports a crash risk during driver cleanup after bsg setup failure, not remote compromise or confidentiality impact.
Researcher notes
The evidence is strongest for a local denial-of-service condition in mpi3mr error cleanup. The source bundle does not provide exploit proof, affected hardware details, or distribution-specific fixed builds. Validate exposure through kernel version, driver use, and vendor backport mapping rather than raw upstream version alone.
Mitigation direction
Apply Linux kernel or distribution updates that include the linked mpi3mr stable fixes.
Check your Linux vendor advisory for exact fixed package versions and backports.
Prioritize systems using mpi3mr-backed storage or affected kernel builds.
Where updates are delayed, reduce unnecessary local access to impacted systems.
Validation and detection
Inventory hosts running Linux kernels in the affected version range.
Confirm whether the mpi3mr driver is present, loaded, or required.
Map installed distro kernel packages to vendor-fixed versions.
Review kernel logs for mpi3mr cleanup crashes or NULL pointer dereferences.
Verify patched kernels include one of the referenced stable commits or vendor equivalent.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.