CVE-2026-98128

What the bug is

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.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/scsi/mpi3mr/mpi3mr_transport.c

What this is

BROADCOM MPI3 STORAGE CONTROLLER DRIVERMAINTAINERS section matched on drivers/scsi/mpi3mr/ · mpi3mr-linuxdrv.pdl@broadcom.com · Supported

Kernel module

mpi3mr

Check it on the machine

grep -w CONFIG_SCSI_MPI3MR /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

lsmod | grep -w mpi3mr

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.

• bookwormm
• trixieMnot built on armel/rpi
• forky, sid, bookworm · linux-6.12m

m

a loadable module on every flavour - check lsmod, can be blacklisted

M

a module where it is built at all; some flavours do not build it

Build switch

CONFIG_SCSI_MPI3MR

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published

2026-09-25 (24 days ago)source

CVSS

no vector published, unrated

Attack vector

not published

EPSS

0.17%, higher than 6.3% of all CVEssource

CISA KEV

not listedthe KEV catalogue

Debian urgency

not yet assignedsource

Subsystem

drivers/scsi

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

Introduced	Fixed in	Commit
6.1	6.1.189	60a9aaac07f6
6.1	6.6.158	58e3d2fbc8c9
6.1	6.12.111	040146f81d09
6.1	6.18.53	06a7073b33b8
6.1	7.2.7	1ccbe8c42009
6.1	7.3	419d129f970a

Debian advisories