scsi: mpi3mr: Fix target device refcount leak in mpi3mr_sas_port_add() (CVE-2026-98128) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-98128

scsi: mpi3mr: Fix target device refcount leak in mpi3mr_sas_port_add()

Answer in brief

CVE-2026-98128 records a Unknown severity vulnerability in scsi: mpi3mr: Fix target device refcount leak in mpi3mr_sas_port_add(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 25, 2026Updated Sep 25, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 25, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=e22bae30667a7e74ed057e00fb6e8c79e0738de3 <040146f81d099006a354b0caacc7f01ca00f257e \|\| >=e22bae30667a7e74ed057e00fb6e8c79e0738de3 <06a7073b33b8f5cb0ee71e07dc669efffb1c7d58 \|\| >=e22bae30667a7e74ed057e00fb6e8c79e0738de3 <1ccbe8c42009706af79e6629c70d42fc929aef2b \|\| >=e22bae30667a7e74ed057e00fb6e8c79e0738de3 <419d129f970aaa6567dbac366b0c93784bf9ec97	040146f81d099006a354b0caacc7f01ca00f257e, 06a7073b33b8f5cb0ee71e07dc669efffb1c7d58, 1ccbe8c42009706af79e6629c70d42fc929aef2b, 419d129f970aaa6567dbac366b0c93784bf9ec97
Linux/Linuxgeneric	6.1	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 040146f81d099006a354b0caacc7f01ca00f257e if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Fix target device refcount leak in mpi3mr_sas_port_add() mpi3mr_get_tgtdev_by_addr() increments the target device kref when it returns a device. If a subsequent error triggers a goto out_fail after the tgtdev reference is acquired, the reference is never released because the out_fail path does not call mpi3mr_tgtdev_put(). This prevents the target device structure from ever being freed. Add a tgtdev put in the out_fail path, guarded by a NULL check since tgtdev is only acquired for SAS_END_DEVICE types and the same cleanup path is shared by earlier error cases where tgtdev is still NULL.

Quoted source text, attributed separately from HOL analysis.