CVE-2026-52974net: tls: fix strparser anchor skb leak on offload RX setup failure
- 7.5HighCVSS base score
- 0.50%Exploitation in 30 daysEPSS · top 57% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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
ID reserved
By Linux
- 15 days later
· 15 days later
Published
- 4 months later
· 4 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Modified | 3.1 | High7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.50% · top 57% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.
Affected products
- affected 84c61fe1a75b4255df1e1e7c054c9e6d048da417 – < 0c9f399b37ce22a5ed94cc51f03ed07ac7f38e32
- affected 84c61fe1a75b4255df1e1e7c054c9e6d048da417 – < 688f12aa44511dd57e448eb670075c6302ad1dc1
- affected 84c61fe1a75b4255df1e1e7c054c9e6d048da417 – < 3c405dfa9619e506e75b8e41f8b29a5b99731877
- affected 84c61fe1a75b4255df1e1e7c054c9e6d048da417 – < 9c54e76f8d6eb11735918777ef0e0509e089557d
- affected 84c61fe1a75b4255df1e1e7c054c9e6d048da417 – < bd07fe6c38b9e44ff3fc02692a53f095c5cc9afc
- affected 84c61fe1a75b4255df1e1e7c054c9e6d048da417 – < 58689498ca3384851145a754dbb1d8ed1cf9fb54
- affected 6.0
- unaffected < 6.0
- unaffected 6.1.175 – ≤ 6.1.*
- unaffected 6.6.141 – ≤ 6.6.*
- unaffected 6.12.91 – ≤ 6.12.*
- unaffected 6.18.33 – ≤ 6.18.*
- unaffected 7.0.10 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References6
- https://git.kernel.org/stable/c/0c9f399b37ce22a5ed94cc51f03ed07ac7f38e32 (opens in a new tab)
- https://git.kernel.org/stable/c/688f12aa44511dd57e448eb670075c6302ad1dc1 (opens in a new tab)
- https://git.kernel.org/stable/c/3c405dfa9619e506e75b8e41f8b29a5b99731877 (opens in a new tab)
- https://git.kernel.org/stable/c/9c54e76f8d6eb11735918777ef0e0509e089557d (opens in a new tab)
- https://git.kernel.org/stable/c/bd07fe6c38b9e44ff3fc02692a53f095c5cc9afc (opens in a new tab)
- https://git.kernel.org/stable/c/58689498ca3384851145a754dbb1d8ed1cf9fb54 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-38842 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-52974)Record last updated .