VDB

CVE-2025-40256

CVE-2025-40256 PUBLISHED

xfrm: also call xfrm_state_delete_tunnel at destroy time for states that were never added

Reported by linux · Published December 4, 2025

In the Linux kernel, the following vulnerability has been resolved: xfrm: also call xfrm_state_delete_tunnel at destroy time for states that were never added In commit b441cf3f8c4b ("xfrm: delete x->tunnel as we delete x"), I missed the case where state creation fails between full initialization (->init_state has been called) and being inserted on the lists. In this situation, ->init_state has been called, so for IPcomp tunnels, the fallback tunnel has been created and added onto the lists, but the user state never gets added, because we fail before that. The user state doesn't go through __xfrm_state_delete, so we don't call xfrm_state_delete_tunnel for those states, and we end up leaking the FB tunnel. There are several codepaths affected by this: the add/update paths, in both net/key and xfrm, and the migrate code (xfrm_migrate, xfrm_state_migrate). A "proper" rollback of the init_state work would probably be doable in the add/update code, but for migrate it gets more complicated as multiple states may be involved. At some point, the new (not-inserted) state will be destroyed, so call xfrm_state_delete_tunnel during xfrm_state_gc_destroy. Most states will have their fallback tunnel cleaned up during __xfrm_state_delete, which solves the issue that b441cf3f8c4b (and other patches before it) aimed at. All states (including FB tunnels) will be removed from the lists once xfrm_state_fini has called flush_work(&xfrm_state_gc_work).

EPSS 0.22% · 12.6th percentile

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
LinuxLinuxf7d879c19d306512c2e260f37e8a3e5c85e37c50, 64441724387b4ac92f67ef51caaaeffe99c950d1, 57b72d74d4651dc19d046308a8304eb9abfe66ac, 1dad653643f28ccc89be93f9440b8804cded85b2, 10deb69864840ccf96b00ac2ab3a2055c0c04721

Risk scores

EPSS Score
0.22%
12.6th percentile

Affected products

VendorProductVersions
LinuxLinux1b28a7fae0128fa140a7dccd995182ff6cd1c67b, 4b2c17d0f9be8b58bb30468bc81a4b61c985b04e, 0da961fa46da1b37ef868d9b603bd202136f8f8e
LinuxLinux6.16, 0, 6.17.10
LinuxLinux*, 6.18, *
linuxlinux_kernel6.16, 6.16

Timeline

  • Dec 4, 2025 CVE Published
  • Dec 5, 2025 EPSS Score (30 in total, the first dated here)
  • Mar 29, 2026 Distribution Patch (147 in total, the first dated here)
  • Mar 29, 2026 Security Advisory (154 in total, the first dated here)
  • Jun 8, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-40256
vulnetix vdb fixes CVE-2025-40256

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-40256/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›