Live › vulnerability › CVE-2026-98559
Go to dashboardThe Linux kernel's SMC (Shared Memory Communications) code traversed a link-group list without holding its lock, so a concurrent termination could free an entry while it was still being read. An attacker could potentially trigger a use-after-free, the sources do not say what they can get beyond a crash or memory corruption.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with the SMC protocol module (net/smc) built in or loaded, which is mainly hosts using SMC-R over RDMA-capable RoCE links. Machines that do not load the smc module are not affected; the sources do not say whether default distribution kernels enable it.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
net/smc: fix UAF on lgr list traversal in smcr_port_err()
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98559")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.