HIGH Introduced in 5.1
smc ClcSock UAF
CVE-2026-99032
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
KernelScan AI7.0HIGH
01Description
In the Linux kernel, the following vulnerability has been resolved: net/smc: protect clcsock lifetime in smc_getname smc_getname() dereferences smc->clcsock without holding clcsock_release_lock. Link-group termination can release the CLC socket through smc_close_active_abort() while the SMC socket is still open, for example after shutdown(SHUT_WR). A getsockname() caller can load smc->clcsock, then the termination worker can clear the pointer and call sock_release() before the caller accesses clcsock->ops or invokes getname(). This causes a use-after-free; if the worker clears the pointer before the load, it causes a NULL dereference. The syscall's file reference keeps the SMC socket alive but does not prevent asynchronous release of its CLC socket. KASAN reported the following with test-only timing instrumentation: BUG: KASAN: slab-use-after-free in smc_getname+0x19e/0x1b0 Read of size 8 at addr ffff888109abb4e0 by task poc/103 Call Trace: smc_getname+0x19e/0x1b0 do_getsockname+0xe5/0x170 __sys_getsockname+0x8c/0x100 Allocated by task 95: sock_alloc_inode+0x1e/0x280 sock_alloc+0x3d/0x240 __sock_create+0x7e/0x430 smc_create+0x121/0x240 Freed by task 0: kmem_cache_free+0xcc/0x340 rcu_core+0x50a/0x1850 Last potentially related work creation: evict+0x446/0x6c0 smc_clcsock_release+0xa8/0xd0 smc_close_active_abort+0x26a/0x3a0 __smc_lgr_terminate.part.0+0x137/0x2e0 Hold clcsock_release_lock across the pointer check and the getname() callback to serialize with smc_clcsock_release(). Return -EBADF if the CLC socket has already been released, preserving the existing peer state check and the callback's return value otherwise.
02KernelScan AI Analysis
Risk summary
A local unprivileged user can trigger a use-after-free in the SMC (Shared Memory Connections) subsystem by racing a getsockname() call against link-group termination. Successful exploitation allows arbitrary kernel memory read and write, leading to privilege escalation or kernel panic. The vulnerability requires the SMC kernel module to be loaded and an SMC socket to be active.
Vulnerability analysis
The smc_getname() function, invoked via the getsockname() syscall, accesses the CLC socket pointer (smc->clcsock) without holding the clcsock_release_lock. Meanwhile, a background termination worker can release that CLC socket through smc_close_active_abort() while the SMC socket remains open (for example after shutdown(SHUT_WR)). This creates a race window where the syscall loads the pointer, the worker frees the socket object, and the syscall then dereferences the stale pointer — causing a use-after-free (or a NULL dereference if the pointer is cleared first). The fix serializes access by taking clcsock_release_lock across the pointer check and the getname() callback, returning -EBADF if the CLC socket has already been released. Any local user who can create or operate on an SMC socket can trigger this race; no special privileges or capabilities are required beyond standard socket access.
Lifecycle
03Fix Versions
| Branch | Introduced | Fixed in | Patch commit |
|---|---|---|---|
| 4.19 | 4.19.299 | 4.20 | 5d0fa089d5ed |
| 5.10 | 5.1 | 5.10.273 | 94a43efd71ad |
| 5.15 | 5.1 | 5.15.224 | 040691998162 |
| 6.1 | 5.1 | 6.1.191 | e607017a553d |
| 6.12 | 5.1 | 6.12.113 | 6a1833f0d7dc |
| 6.18 | 5.1 | 6.18.57 | c223da71abfa |
| 6.6 | 5.1 | 6.6.160 | 1512e3714b39 |
| 7.2 | 5.1 | 7.2.11 | 64a6b36b0e18 |
| mainline | 5.1 | 7.3 | — |
| cip/6.12 | 5.1 | 6.12.114-cip34 | 1512e3714b39 |
04CIP Kernels
State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.
| CIP tree | State |
|---|---|
| cip/6.12 | Fixed in 6.12.114-cip34 |
| cip/6.1 | Affected — no CIP fix yet (latest 6.1.190-cip62) |
| cip/6.1-rt | Affected — no CIP fix yet (latest 6.1.189-cip61-rt32) |
| cip/5.10 | Affected — no CIP fix yet (latest 5.10.272-cip79) |
| cip/5.10-rt | Affected — no CIP fix yet (latest 5.10.272-cip79-rt35) |
| cip/4.19 | Affected — no CIP fix yet (latest 4.19.325-cip136) |
| cip/4.19-rt | Affected — no CIP fix yet (latest 4.19.325-cip136-rt50) |