Look up another CVE · open CVE-2026-98559 in the interactive tracker
CVE-2026-98559
net/smc: fix UAF on lgr list traversal in smcr_port_err()
Published 2026-10-18 (today) by the Linux kernel CNA. Subsystem net/smc. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-98559 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixed | 6.1.190-1 | Update the kernel and reboot. Fixed in 6.1.190-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.113-1 | Update the kernel and reboot. Fixed in 6.12.113-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.9-1 | Update the kernel and reboot. Fixed in 7.2.9-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.9-1 | Update the kernel and reboot. Fixed in 7.2.9-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
smcr_port_err() traverses smc_lgr_list.list without holding smc_lgr_list.lock, allowing a concurrent smc_lgr_terminate_sched() to free an lgr while it is still being dereferenced. Hold smc_lgr_list.lock across the traversal. Update smc_ib_gid_check() to call smcr_port_err() after releasing the lock.
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.
net/smc/smc_core.c
net/smc/smc_ib.c
- What this is
- SHARED MEMORY COMMUNICATIONS (SMC) SOCKETSMAINTAINERS section matched on net/smc/ · linux-rdma@vger.kernel.org · Supported
- Kernel module
- smc
Check it on the machine
grep -w CONFIG_SMC /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 smcPrints 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 does not build this code in 2 releases. It does build it in 2 releases, so the answer depends on which release the machine runs.
- bookworm, trixiem
- forky, sidn
- m
- a loadable module on every flavour - check lsmod, can be blacklisted
- n
- not enabled on any flavour - this release does not build the code
- Build switch
- CONFIG_SMC
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-10-18 (today)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- not scored
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- net/smc
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.8 | 5.15.222 | 34bcf11cd252 |
| 5.8 | 6.1.189 | 0edcc4284392 |
| 5.8 | 6.6.158 | 00a59600ae72 |
| 5.8 | 6.12.112 | 3d35f069e1c1 |
| 5.8 | 6.18.55 | 3d65a2eb4449 |
| 5.8 | 7.2.9 | a9b968e42690 |
| 5.8 | 7.3 | 61cb282fe97b |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2026-98559, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.