Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLocal access to host with mpi3mr HBA
-
ExploitTrigger SAS port add under memory pressure
-
Executionsas_port_alloc_num() returns NULL, unchecked dereference
-
ImpactKernel panic (denial of service)
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Null pointer safety, defensive checks
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires the mpi3mr driver to be loaded, which means the host must have a Broadcom/LSI MPI 3.0 tri-mode SAS/SATA HBA present. The specific trigger is a kernel memory allocation failure causing sas_port_alloc_num() to return NULL during mpi3mr_sas_port_add() (the secondary leak path requires sas_port_add() itself to fail). Limiting factors that reduce realistic risk: the vector is local only (AV:L), it affects only systems with this specific storage hardware/driver, the triggering allocation failure is not normally attacker-controlled (so it typically manifests under memory pressure at device discovery/hotplug rather than on demand), and impact is confined to a kernel crash (denial of service) with no confidentiality or integrity effect. |
| Impact | This is a medium-severity Linux kernel robustness fix, not a high-priority emergency. The signals are consistent and point to low real-world risk: the NVD CVSS is 5.5 with vector AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - local attack vector, low privileges, no confidentiality or integrity impact, and availability-only impact (a kernel crash). EPSS is 0.17% (5th percentile), i.e. very low exploitation probability, which aligns with the absence of a CISA KEV listing and no public exploit reference in the input. No SSVC decision fields (exploitation status, automatable, technical impact) were supplied, so that framework cannot be cross-referenced; the only priority signal provided is the vuln.today 'this_month' label, which is a routine-patching cadence, not act_now/emergency. One discrepancy worth verifying with the vendor: NVD assigns AC:L, but the description states the NULL dereference occurs specifically 'on memory allocation failure' in sas_port_alloc_num() - an allocation failure is not normally under attacker control, which argues for higher attack complexity and weaker local triggerability than AC:L implies. Overall this reads as a defensive hardening patch for a specific storage driver rather than a widely exploitable flaw. |
| Exploit ScenarioDerived | On a system using the mpi3mr driver (Broadcom/LSI MPI 3.0 tri-mode SAS/SATA HBA), a kernel memory allocation failure during SAS port addition causes sas_port_alloc_num() to return NULL; because the result is passed to sas_port_add() without a NULL check, the kernel dereferences the NULL pointer and panics, producing a denial of service. Realistically this surfaces under memory pressure during device discovery or hotplug rather than through direct attacker control. No public exploit was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 22, 2026
A NULL pointer dereference in the Linux kernel's mpi3mr SCSI driver (mpi3mr_sas_port_add()) can crash the host when sas_port_alloc_num() returns NULL after a memory allocation failure and the result is passed unchecked into sas_port_add(); a second path in the same function leaks the allocated sas_port structure when sas_port_add() itself fails. Exposure is limited to systems running an affected kernel on hardware with a Broadcom/LSI MPI 3.0 tri-mode SAS/SATA HBA, since the mpi3mr module must be loaded for the code to be reachable, and the trigger is a kernel allocation failure rather than a condition an attacker directly controls, so it typically surfaces under memory pressure during device discovery or hotplug. Impact is a kernel crash (denial of service) with no confidentiality or integrity effect; EPSS is 0.17% (5th percentile), there is no CISA KEV listing, and no public exploit identified at time of analysis. Vendor patches are available in the 6.12.111, 6.18.53, 7.2.7 and 7.3-rc2 releases.
RemediationAI
Vendor-released patches are available: update to Linux 6.12.111, 6.18.53 or 7.2.7 (or 7.3-rc2 / later) for the branch you run, or apply the corresponding stable commit from the advisory set (5c50137ba11b6e20e7074303dae35ff58d5a0b6f, 2f69ed909de9e3d46af9db7dd24b9b80dc31b5ec, 5cb58b052cf09dd8e88d92c1d649b3eea5c95d4d, dba9e2181ca5e875f98b8b9b4535cdaab87dcb0d, 7e3489b5950e7668355762968a7c7f75fe9bc80d, c848a1bbe110496eff8dcdf7cfbff66a69edae89) and see https://nvd.nist.gov/vuln/detail/CVE-2026-98129 and https://vuldb.com/vuln/409964 for tracking. Because the defect lives in mpi3mr_sas_port_add() and is only reachable when the mpi3mr driver is bound to a Broadcom/LSI MPI 3.0 tri-mode HBA, hosts without that hardware carry no exposure and hosts that do not need the adapter can avoid the code path by not loading the mpi3mr module - with the trade-off that the attached SAS/SATA storage becomes unavailable. There is no indication of active exploitation or public exploit code, so scheduling the kernel update in the normal monthly patch cycle is consistent with the current priority assessment.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The mpi3mr driver supports Broadcom/LSI MPI 3.0 tri-mode SAS/SATA host bus adapters and integrates with libsas for SAS topology and port management. In mpi3mr_sas_port_add(), the port object is obtained via sas_port_alloc_num(), which can return NULL on memory allocation failure; the code passed that return value directly to sas_port_add() without a NULL check, producing a NULL pointer dereference (CWE-476) that faults the kernel. The same fix also addresses a resource-handling defect: when sas_port_add() fails, the previously allocated sas_port was not released before the error path jumped to out_fail, leaking the structure, so the patch adds sas_port_free() on that path. The available sources do not describe any further trigger mechanism beyond the allocation failure, and the flaw is purely a robustness/error-path defect reachable only with the driver loaded; the assessed vector (AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H) reflects local access, a harder-to-achieve trigger tied to memory exhaustion, and availability-only impact.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Local storage-driver crash (AV:L, A:H only); AC:H because the description ties the trigger to a memory allocation failure not under normal attacker control; PR:L as some local presence is needed.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionNVD
In the Linux kernel, the following vulnerability has been resolved:
scsi: mpi3mr: Fix NULL pointer dereference in mpi3mr_sas_port_add()
sas_port_alloc_num() can return NULL on memory allocation failure. The return value is passed directly to sas_port_add() without a NULL check, which causes a NULL pointer dereference.
Additionally, if sas_port_add() fails, the allocated port is not freed before jumping to out_fail, leaking the sas_port structure. Call sas_port_free() to properly release it.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A null pointer dereference occurs when a program attempts to access memory through a pointer that has been set to NULL (address 0x0).
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
EUVD-2026-86960
GHSA-7v7j-6hjx-3w6v
NVD
CVE.org
EPSS
VulDB
Exploit-DB