Skip to main content
← All vulnerabilities
CVE-2026-64541

net/smc: fix UAF in smc_cdc_rx_handler() by pinning the socket

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, and 2 more
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: total

Summary

In the Linux kernel, the following vulnerability has been resolved: net/smc: fix UAF in smc_cdc_rx_handler() by pinning the socket smc_cdc_rx_handler() looks up the connection by token under the link group's conns_lock, drops the lock, and then dereferences conn and the smc_sock derived from it, ending in sock_hold(&smc->sk) inside smc_cdc_msg_recv(). No reference is held across the lock release. The only reference pinning the socket while the connection is discoverable in the link group is taken in smc_lgr_register_conn() (sock_hold) and dropped in __smc_lgr_unregister_conn() (sock_put), both under conns_lock. Once the handler drops conns_lock, a concurrent close() -> smc_release() -> smc_conn_free() -> smc_lgr_unregister_conn() can drop that reference and free the smc_sock, so the handler's later sock_hold() runs on freed memory: WARNING: lib/refcount.c:25 at refcount_warn_saturate Workqueue: rxe_wq do_work refcount_warn_saturate (lib/refcount.c:25) smc_cdc_msg_recv (net/smc/smc_cdc.c:430) smc_cdc_rx_handler (net/smc/smc_cdc.c:502) smc_wr_rx_tasklet_fn (net/smc/smc_wr.c:445) tasklet_action_common (kernel/softirq.c:938) handle_softirqs (kernel/softirq.c:622) Kernel panic - not syncing: panic_on_warn set Only SMC-R is affected. The SMC-D receive tasklet is stopped by tasklet_kill(&conn->rx_tsklet) in smc_conn_free() before the connection is unregistered, so it cannot run concurrently with the free. Take the socket reference while still holding conns_lock, so the registration reference can no longer be the last one, and drop it once the handler is done.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  3. Record last updated

Affected versions

  • Linux Linux

    From d7b0e37c1ac152905b18a5b9506179091a35b0b6 · fixed in 8de4f665d0febfb92803dece377791a563fc7041; From d7b0e37c1ac152905b18a5b9506179091a35b0b6 · fixed in 8145b432136285e01091815b48ceb2dae261f262; From d7b0e37c1ac152905b18a5b9506179091a35b0b6 · fixed in 1951bffbc6493ec34cff3956b29d4bc6606904a6; From d7b0e37c1ac152905b18a5b9506179091a35b0b6 · fixed in 647b19e5cc145a2f1f685ae8ff3805a17356888c; From d7b0e37c1ac152905b18a5b9506179091a35b0b6 · fixed in 472e9d7c0d5b03be3ff91ff941f57da822b031bc; From d7b0e37c1ac152905b18a5b9506179091a35b0b6 · fixed in 3bfb96d9bc6a7ed0b99c7db329cc2e22a28d84bb; From d7b0e37c1ac152905b18a5b9506179091a35b0b6 · fixed in ce5aa8084329351086894aa34d77e40301d5bd3d; From d7b0e37c1ac152905b18a5b9506179091a35b0b6 · fixed in 9d160b35cc34a2ba8229d07651468a7848325135

  • Linux Linux

    4.18

  • KernelLinux

    From 4.18.0 · fixed in 5.10.261; From 5.11.0 · fixed in 5.15.212; From 5.16.0 · fixed in 6.1.178; From 6.2.0 · fixed in 6.6.145; From 6.7.0 · fixed in 6.12.97; From 6.13.0 · fixed in 6.18.40; From 6.19.0 · fixed in 7.1.5

References 8

git.kernel.org