CVE-2026-68415
xfrm: clear mode callbacks after failed mode setup
Reported by linux · Published August 10, 2026
In the Linux kernel, the following vulnerability has been resolved: xfrm: clear mode callbacks after failed mode setup xfrm_state_gc_task can run long after a failed IPTFS state setup. In the reproduced case, __xfrm_init_state() cached x->mode_cbs, IPTFS setup returned -ENOMEM before publishing mode_data, and the temporary module reference from xfrm_get_mode_cbs() was dropped immediately. The dead state then kept x->mode_cbs until deferred GC ran after xfrm_iptfs had been unloaded. Clear x->mode_cbs when mode init or clone fails before publishing mode_data. Those states never installed mode-specific state or the long-term IPTFS module pin, so deferred GC has nothing mode-specific to destroy and must not retain a callback table pointer past the temporary lookup reference. The buggy scenario involves two paths, with each column showing the order within that path: failed setup path: 1. cache x->mode_cbs 2. mode setup fails before mode_data 3. drop the temporary module ref 4. dead state keeps x->mode_cbs cached GC/unload path: 1. xfrm_state_put() queues GC work 2. xfrm_iptfs unloads later 3. xfrm_state_gc_task runs 4. GC dereferences stale x->mode_cbs This also covers the failed clone path where clone_state() returns before publishing mode_data. Validation reproduced this kernel report: Kernel panic - not syncing: Fatal exception CONFIG_FAULT_INJECTION_STACKTRACE_FILTER=y failslab_stacktrace_filter matched xfrm_iptfs frames ack_error=-12 FAULT_INJECTION: forcing a failure BUG: unable to handle page fault Workqueue: events xfrm_state_gc_task RIP: xfrm_state_gc_task+0x142/0x650 Modules linked in: esp4_offload xfrm_user [last unloaded: xfrm_iptfs] Kernel panic - not syncing: Fatal exception
EPSS 0.13% · 2.9th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Linux | Linux | c37a079230128a5237f45fb4e181bc069a5c2955, 9845a35986a658816f7752f7ebd7c455a4c7dfdf, 2538bd3cd1ff5af655908469544ac7b7ae259386 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 4b3faf610cc63bfac972711635eafbca5e7d7117, 4b3faf610cc63bfac972711635eafbca5e7d7117, 4b3faf610cc63bfac972711635eafbca5e7d7117 |
| Linux | Linux | 6.14, 0, 6.18.42 |
| Linux | Linux | 7.2, 0, 6.18.42 |
| linux | linux_kernel | 6.14, 6.14, 6.14 |
Timeline
- Aug 10, 2026 Coalition ESS Score
- Aug 10, 2026 CVE Published
- Aug 17, 2026 CVE Updated
- Aug 21, 2026 Security Advisory
- Aug 24, 2026 EPSS Score (10 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-68415
vulnetix vdb fixes CVE-2026-68415
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-2026-68415/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart