net: tls: fix strparser anchor skb leak on offload RX setup failure
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: net: tls: fix strparser anchor skb leak on offload RX setup failure When tls_set_device_offload_rx() fails at tls_dev_add(), the error path calls tls_sw_free_resources_rx() to clean up the SW context that was initialized by tls_set_sw_offload(). This function calls tls_sw_release_resources_rx() (which stops the strparser via tls_strp_stop()) and tls_sw_free_ctx_rx() (which kfrees the context), but never frees the anchor skb that was allocated by alloc_skb(0) in tls_strp_init(). Note that tls_sw_free_resources_rx() is exclusively used for this "failed to start offload" code path, there's no other caller. The leak did not exist before commit 84c61fe1a75b ("tls: rx: do not use the standard strparser"), because the standard strparser doesn't try to pre-allocate an skb. The normal close path in tls_sk_proto_close() handles cleanup by calling tls_sw_strparser_done() (which calls tls_strp_done()) after dropping the socket lock, because tls_strp_done() does cancel_work_sync() and the strparser work handler takes the socket lock.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 84c61fe1a75b4255df1e1e7c054c9e6d048da417 · fixed in 0c9f399b37ce22a5ed94cc51f03ed07ac7f38e32; From 84c61fe1a75b4255df1e1e7c054c9e6d048da417 · fixed in 688f12aa44511dd57e448eb670075c6302ad1dc1; From 84c61fe1a75b4255df1e1e7c054c9e6d048da417 · fixed in 3c405dfa9619e506e75b8e41f8b29a5b99731877; From 84c61fe1a75b4255df1e1e7c054c9e6d048da417 · fixed in 9c54e76f8d6eb11735918777ef0e0509e089557d; From 84c61fe1a75b4255df1e1e7c054c9e6d048da417 · fixed in bd07fe6c38b9e44ff3fc02692a53f095c5cc9afc; From 84c61fe1a75b4255df1e1e7c054c9e6d048da417 · fixed in 58689498ca3384851145a754dbb1d8ed1cf9fb54
- Linux Linux
6.0
- KernelLinux
From 6.0.0 · fixed in 6.1.175; From 6.2.0 · fixed in 6.6.141; From 6.7.0 · fixed in 6.12.91; From 6.13.0 · fixed in 6.18.33; From 6.19.0 · fixed in 7.0.10