CVE-2026-90415

What the bug is

write_tpt_entry() allocates a new STAG index with c4iw_get_resource() and bumps stats.stag.cur before programming the entry. When write_adapter_mem() fails, it returns the error without releasing the index or reversing the statistic. No MR is inserted into rhp->mrs, so deregistration never reclaims it, leaking the index until device teardown. Record whether this call allocated the index and, on a failed write, return it to tpt_table and decrement stats.stag.cur. Key the rollback on both the write error and that flag, not the error alone: a non-reset update carries a caller-owned STAG that this call did not allocate and must not free.

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/infiniband/hw/cxgb4/mem.c

What this is

CXGB4 IWARP RNIC DRIVER (IW_CXGB4)MAINTAINERS section matched on drivers/infiniband/hw/cxgb4/ · linux-rdma@vger.kernel.org · Supported

Kernel module

iw_cxgb4

Check it on the machine

grep -wE 'CONFIG_INFINIBAND|CONFIG_INFINIBAND_CXGB4' /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 iw_cxgb4

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.

• bookwormMnot built on amd64/cloud-amd64, arm64/cloud-arm64
• trixieMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armel/rpi
• forky, sid, bookworm · linux-6.12Mnot built on amd64/cloud-amd64, arm64/cloud-arm64

M

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

Build switches

CONFIG_INFINIBAND, CONFIG_INFINIBAND_CXGB4

Reads as

all on means the file is compiled; any one off means it is not.

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-17 (31 days ago)source

CVSS

no vector published, unrated

Attack vector

not published

EPSS

0.18%, higher than 6.7% of all CVEssource

CISA KEV

not listedthe KEV catalogue

Debian urgency

not yet assignedsource

Subsystem

drivers/infiniband

Upstream fixes

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

Introduced	Fixed in	Commit
3.5	5.10.270	5fe4731bfbd8
3.5	5.15.221	8f6976d635d1
3.5	6.1.188	9eeafcda1d6c
3.5	6.6.157	5a21e5114cec
3.5	6.12.110	2f17ca7ab526
3.5	6.18.52	a2e37d1ab773
3.5	7.2.6	a64e2beb4501
3.5	7.3	fdfb5cea4bf0

Debian advisories