CVE-2026-52974

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: tls: fix strparser anchor skb leak on offload RX setup failure<br /> <br /> When tls_set_device_offload_rx() fails at tls_dev_add(), the error path<br /> calls tls_sw_free_resources_rx() to clean up the SW context that was<br /> initialized by tls_set_sw_offload(). This function calls<br /> tls_sw_release_resources_rx() (which stops the strparser via<br /> tls_strp_stop()) and tls_sw_free_ctx_rx() (which kfrees the context),<br /> but never frees the anchor skb that was allocated by alloc_skb(0) in<br /> tls_strp_init().<br /> <br /> Note that tls_sw_free_resources_rx() is exclusively used for this<br /> "failed to start offload" code path, there&amp;#39;s no other caller.<br /> <br /> The leak did not exist before commit 84c61fe1a75b ("tls: rx: do not use<br /> the standard strparser"), because the standard strparser doesn&amp;#39;t try<br /> to pre-allocate an skb.<br /> <br /> The normal close path in tls_sk_proto_close() handles cleanup by calling<br /> tls_sw_strparser_done() (which calls tls_strp_done()) after dropping<br /> the socket lock, because tls_strp_done() does cancel_work_sync() and<br /> the strparser work handler takes the socket lock.