CVE-2026-52974
Last modified
CVE-2026-52974 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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.. EPSS estimates a 0.51% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.0, < 6.1.175 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.141 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.91 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.33 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.10 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-52974?
How severe is CVE-2026-52974?
How do I fix CVE-2026-52974?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-52969In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-5297Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2026-52970In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-52971In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-52972In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-52973In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-52975In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-52976In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-52977In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-52978In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-52979In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-52980In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-52974?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
