net/smc: fix socket use-after-free during link group termination
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 69318b5215f2dc32c345a3d65b98b4b1bf29c007 · < f807a63d0d95680c34f677700da9148a07d7c78f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net/smc: fix socket use-after-free during link group termination
__smc_lgr_terminate() drops conns_lock after finding a connection in lgr->conns_all, but before taking a reference on its socket. The connection is embedded in the socket, and its registration reference protects it only while the connection remains in the tree.
A concurrent close can unregister the connection and drop that reference, freeing the socket before the termination worker reaches sock_hold().
The race is reachable when close overlaps link group termination. Local stress testing reproduced the use-after-free and KASAN reported:
BUG: KASAN: slab-use-after-free in __smc_lgr_terminate.part.0 [smc] Write of size 4 by task kworker/3:3 Workqueue: events smc_lgr_terminate_work [smc] __smc_lgr_terminate.part.0 [smc]
The socket was allocated by smc_create(), freed through slab_free_after_rcu_debug(), and was followed by:
refcount_t: addition on 0; use-after-free. __smc_lgr_terminate.part.0 [smc]
From the CVE record · Linux
The Linux kernel’s net/smc code can use a socket after it has been freed when a connection close overlaps link group termination. Local stress testing reproduced the race; the input does not establish a network attack path, authentication requirements, or user-interaction requirements.
Engineers running Linux kernels with net/smc should check whether their kernel includes the fix; affected versions were not provided.