Answer in brief
CVE-2025-40215 records a High severity (CVSS 7.8) vulnerability in xfrm: delete x->tunnel as we delete x. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9d4139c76905833afcb77fe8ccc17f302a0eb9ab <1b28a7fae0128fa140a7dccd995182ff6cd1c67b || >=9d4139c76905833afcb77fe8ccc17f302a0eb9ab <4b2c17d0f9be8b58bb30468bc81a4b61c985b04e || >=9d4139c76905833afcb77fe8ccc17f302a0eb9ab <0da961fa46da1b37ef868d9b603bd202136f8f8e || >=9d4139c76905833afcb77fe8ccc17f302a0eb9ab <d0e0d1097118461463b76562c7ebaabaa5b90b13 || >=9d4139c76905833afcb77fe8ccc17f302a0eb9ab <dc3636912d41770466543623cb76e7b88fdb42c7 || >=9d4139c76905833afcb77fe8ccc17f302a0eb9ab <b441cf3f8c4b8576639d20c8eb4aa32917602ecd | 1b28a7fae0128fa140a7dccd995182ff6cd1c67b, 4b2c17d0f9be8b58bb30468bc81a4b61c985b04e, 0da961fa46da1b37ef868d9b603bd202136f8f8e, d0e0d1097118461463b76562c7ebaabaa5b90b13, dc3636912d41770466543623cb76e7b88fdb42c7, b441cf3f8c4b8576639d20c8eb4aa32917602ecd |
| Linux/Linuxgeneric | 2.6.29 | Not reported |
Published upstream
Dec 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: xfrm: delete x->tunnel as we delete x The ipcomp fallback tunnels currently get deleted (from the various lists and hashtables) as the last user state that needed that fallback is destroyed (not deleted). If a reference to that user state still exists, the fallback state will remain on the hashtables/lists, triggering the WARN in xfrm_state_fini. Because of those remaining references, the fix in commit f75a2804da39 ("xfrm: destroy xfrm_state synchronously on net exit path") is not complete. We recently fixed one such situation in TCP due to defered freeing of skbs (commit 9b6412e6979f ("tcp: drop secpath at the same time as we currently drop dst")). This can also happen due to IP reassembly: skbs with a secpath remain on the reassembly queue until netns destruction. If we can't guarantee that the queues are flushed by the time xfrm_state_fini runs, there may still be references to a (user) xfrm_state, preventing the timely deletion of the corresponding fallback state. Instead of chasing each instance of skbs holding a secpath one by one, this patch fixes the issue directly within xfrm, by deleting the fallback state as soon as the last user state depending on it has been deleted. Destruction will still happen when the final reference is dropped. A separate lockdep class for the fallback state is required since we're going to lock x->tunnel while x is locked.
Quoted source text, attributed separately from HOL analysis.