CVE-2026-64541
CVE CVE-2026-64541EUVD EUVD-2026-49592Published 2026-07-27T20:10:34.000ZLast changed 2026-08-05T12:42:49.000ZCVSS 9.8
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 0; d7b0e37c1ac152905b18a5b9506179091a35b0b6 <8145b432136285e01091815b48ceb2dae261f262; patch: 7.2-rc3; d7b0e37c1ac152905b18a5b9506179091a35b0b6 <647b19e5cc145a2f1f685ae8ff3805a17356888c; 4.18; patch: 6.18.40; patch: 6.6.145; d7b0e37c1ac152905b18a5b9506179091a35b0b6 <472e9d7c0d5b03be3ff91ff941f57da822b031bc; patch: 7.1.5; patch: 6.12.97; d7b0e37c1ac152905b18a5b9506179091a35b0b6 <9d160b35cc34a2ba8229d07651468a7848325135; d7b0e37c1ac152905b18a5b9506179091a35b0b6 <ce5aa8084329351086894aa34d77e40301d5bd3d; d7b0e37c1ac152905b18a5b9506179091a35b0b6 <8de4f665d0febfb92803dece377791a563fc7041; patch: 5.10.261; patch: 5.15.212; patch: 6.1.178; d7b0e37c1ac152905b18a5b9506179091a35b0b6 <3bfb96d9bc6a7ed0b99c7db329cc2e22a28d84bb; d7b0e37c1ac152905b18a5b9506179091a35b0b6 <1951bffbc6493ec34cff3956b29d4bc6606904a6
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.