GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux net/smc: connection freed before tasklet drain leaves a use-after-free on the SMC-D receive path

UnscoredCVE-2026-80979Kernel, userspace & hypervisorcurated

Impact

smc_conn_free() only unregisters the connection while the link group is still on the device list and never sets conn->killed, so a connection freed during the window opened by smc_lgr_terminate_sched() keeps its smcd->conn[] slot live. The device can then re-arm the receive tasklet after tasklet_kill() returned, and on the DMB-nocopy path the tasklet dereferences a send buffer that was just freed - a use-after-free in the network receive path, reachable from remote peers that can drive SMC link-group termination. SMC-D is used for high-throughput RDMA-style socket traffic between hosts, so on a fabric shared across tenants this is a kernel-memory bug driven by the other end of a connection rather than by local code.

Who can reach it

A peer able to establish SMC connections to the host and cause a link group to terminate, plus the SMC-D device driving the receive tasklet. Only hosts with SMC (s390 ISM or SMC-R over RoCE) configured and in use are affected; a node with no SMC sockets never reaches this code.

What to do

Take the stable kernel update with the fix and reboot the node. If SMC is not actually in use on the fleet - the common case outside s390 and specific RoCE deployments - keep the smc module unloaded or blacklisted, which removes the exposure without a maintenance window.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.