CVE-2026-64541
Linux kernel vulnerability
- Published27 Jul 2026
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://git.kernel.org/stable/c/1951bffbc6493ec34cff3956b29d4bc6606904a6
- https://git.kernel.org/stable/c/3bfb96d9bc6a7ed0b99c7db329cc2e22a28d84bb
- https://git.kernel.org/stable/c/472e9d7c0d5b03be3ff91ff941f57da822b031bc
- https://git.kernel.org/stable/c/647b19e5cc145a2f1f685ae8ff3805a17356888c
- https://git.kernel.org/stable/c/8145b432136285e01091815b48ceb2dae261f262
- https://git.kernel.org/stable/c/8de4f665d0febfb92803dece377791a563fc7041
- https://git.kernel.org/stable/c/9d160b35cc34a2ba8229d07651468a7848325135
- https://git.kernel.org/stable/c/ce5aa8084329351086894aa34d77e40301d5bd3d
Frequently asked
Is CVE-2026-64541 being actively exploited?
CVE-2026-64541 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.56%.
How severe is CVE-2026-64541?
CVE-2026-64541 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.56% probability of exploitation.
How do I fix CVE-2026-64541?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-64541 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.