CVE-2025-21864
Last modified
CVE-2025-21864 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: tcp: drop secpath at the same time as we currently drop dst Xiumei reported hitting the WARN in xfrm6_tunnel_net_exit while running tests that boil down to: - create a pair of netns - run a basic TCP test over ipcomp6 - delete the pair of netns The xfrm_state found on spi_byaddr was not deleted at the time we delete the netns, because we still have a reference on it. This lingering reference comes from a secpath (which holds a ref on the xfrm_state), which is still attached to an skb. EPSS estimates a 0.21% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: tcp: drop secpath at the same time as we currently drop dst Xiumei reported hitting the WARN in xfrm6_tunnel_net_exit while running tests that boil down to: - create a pair of netns - run a basic TCP test over ipcomp6 - delete the pair of netns The xfrm_state found on spi_byaddr was not deleted at the time we delete the netns, because we still have a reference on it. This lingering reference comes from a secpath (which holds a ref on the xfrm_state), which is still attached to an skb. This skb is not leaked, it ends up on sk_receive_queue and then gets defer-free'd by skb_attempt_defer_free. The problem happens when we defer freeing an skb (push it on one CPU's defer_list), and don't flush that list before the netns is deleted. In that case, we still have a reference on the xfrm_state that we don't expect at this point. We already drop the skb's dst in the TCP receive path when it's no longer needed, so let's also drop the secpath. At this point, tcp_filter has already called into the LSM hooks that may require the secpath, so it should not be needed anymore. However, in some of those places, the MPTCP extension has just been attached to the skb, so we cannot simply drop all extensions.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.19, < 6.1.130 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.80 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.17 | — |
| Linux | Linux Kernel | >= 6.13, < 6.13.5 | — |
| Linux | Linux Kernel | 6.14 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-21864?
How severe is CVE-2025-21864?
How do I fix CVE-2025-21864?
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 2025
- CVE-2025-21859In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-2186The Recover WooCommerce Cart Abandonment, Newsletter, Email …7.5
- CVE-2025-21860In the Linux kernel, the following vulnerability has been re…3.3
- CVE-2025-21861In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21862In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21863In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-21865In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21866In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21867In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-21868In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21869In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-21870In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2025-21864?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
