PatchSiren cyber security CVE debrief
CVE-2026-98128 Linux CVE debrief
A vulnerability in the Linux kernel's scsi: mpi3mr component can cause a target device refcount leak, potentially preventing the target device structure from being freed. This issue arises when mpi3mr_sas_port_add() acquires a reference to a target device using mpi3mr_get_tgtdev_by_addr(), but fails to release it in case of an error. The fix involves adding a tgtdev put in the out_fail path, guarded by a NULL check. Linux kernel maintainers and administrators should verify and apply patches, monitor system logs, and assess exposure based on their specific Linux kernel version and configuration.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-25
- Original CVE updated
- 2026-09-25
- Advisory published
- 2026-09-25
- Advisory updated
- 2026-09-25
Who should care
Linux kernel maintainers, administrators, and users of systems with the scsi: mpi3mr component should verify Linux kernel version and scsi: mpi3mr component configuration to ensure patch application, monitor system logs for potential issues related to target device refcount leak, and assess exposure based on their specific Linux kernel version and configuration.
Why it matters
A vulnerability in the Linux kernel's scsi: mpi3mr component can cause a target device refcount leak, potentially preventing the target device structure from being freed. Defenders should verify and apply patches, monitor system logs, and assess exposure based on their specific Linux kernel version and configuration.
- Verify Linux kernel version and scsi: mpi3mr component configuration to ensure patch application
- Monitor system logs for potential issues related to target device refcount leak
Technical summary
The Linux kernel's scsi: mpi3mr component has a vulnerability that can cause a target device refcount leak. This occurs when mpi3mr_sas_port_add() acquires a reference to a target device using mpi3mr_get_tgtdev_by_addr(), but fails to release it in case of an error. The issue is resolved by adding a tgtdev put in the out_fail path, guarded by a NULL check. This fix prevents the target device structure from being freed, addressing the vulnerability in the Linux kernel's scsi: mpi3mr component. Defenders should focus on verifying and applying patches for the Linux kernel scsi: mpi3mr component.
Defensive priority
Verify and apply patches for Linux kernel scsi: mpi3mr component
Recommended defensive actions
- Verify Linux kernel version and scsi: mpi3mr component configuration
- Apply patches from kernel.org
- Monitor system logs for potential issues
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and source references indicate a refcount leak in the Linux kernel's scsi: mpi3mr component. However, details on exploitation, impact, and affected versions are limited. Defenders should verify Linux kernel version and scsi: mpi3mr component configuration, apply patches from kernel.org, and monitor system logs for potential issues related to target device refcount leak.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-98128 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-98128
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-98128 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-98128
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/040146f81d099006a354b0caacc7f01ca00f257e
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/06a7073b33b8f5cb0ee71e07dc669efffb1c7d58
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/1ccbe8c42009706af79e6629c70d42fc929aef2b
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/419d129f970aaa6567dbac366b0c93784bf9ec97
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.