Answer in brief
CVE-2026-63911 records a Unknown severity vulnerability in xfrm: iptfs: reset runtime state when cloning SAs. 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.
A CVSS score is not reported in the current record. 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 | >=0e4fbf013fa566f274ce9b4ce698c75b1f998c52 <9327252e04626d4bb02ca8c0c108fbe8eabf0c5a || >=0e4fbf013fa566f274ce9b4ce698c75b1f998c52 <dfb9f6cbfa9826655a49698cf90eb800fce2178e || >=0e4fbf013fa566f274ce9b4ce698c75b1f998c52 <7f83d174073234839aea176f265e517e0d50a1d2 | 9327252e04626d4bb02ca8c0c108fbe8eabf0c5a, dfb9f6cbfa9826655a49698cf90eb800fce2178e, 7f83d174073234839aea176f265e517e0d50a1d2 |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 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: iptfs: reset runtime state when cloning SAs iptfs_clone_state() clones the IPTFS mode data with kmemdup(). This copies runtime objects which must not be shared with the original SA, including the embedded sk_buff_head, hrtimers, spinlock, and in-flight reassembly/reorder state. If xfrm_state_migrate() fails after clone_state() but before the later init_state() call has reinitialized those fields, the cloned state can be destroyed by xfrm_state_gc_task() with list and timer state copied from the original SA. With queued packets this lets the clone splice and free skbs owned by the original IPTFS queue, leading to use-after-free and double-free reports in iptfs_destroy_state() and skb release paths. Reinitialize the clone's runtime state before publishing it through x->mode_data. Because clone_state() now publishes a destroyable mode_data object before init_state(), take the mode callback module reference there. Avoid taking it again from __iptfs_init_state() for the same object.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-63911 records a Unknown severity vulnerability in xfrm: iptfs: reset runtime state when cloning SAs. 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.
A CVSS score is not reported in the current record. 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 | >=0e4fbf013fa566f274ce9b4ce698c75b1f998c52 <9327252e04626d4bb02ca8c0c108fbe8eabf0c5a || >=0e4fbf013fa566f274ce9b4ce698c75b1f998c52 <dfb9f6cbfa9826655a49698cf90eb800fce2178e || >=0e4fbf013fa566f274ce9b4ce698c75b1f998c52 <7f83d174073234839aea176f265e517e0d50a1d2 | 9327252e04626d4bb02ca8c0c108fbe8eabf0c5a, dfb9f6cbfa9826655a49698cf90eb800fce2178e, 7f83d174073234839aea176f265e517e0d50a1d2 |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 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: iptfs: reset runtime state when cloning SAs iptfs_clone_state() clones the IPTFS mode data with kmemdup(). This copies runtime objects which must not be shared with the original SA, including the embedded sk_buff_head, hrtimers, spinlock, and in-flight reassembly/reorder state. If xfrm_state_migrate() fails after clone_state() but before the later init_state() call has reinitialized those fields, the cloned state can be destroyed by xfrm_state_gc_task() with list and timer state copied from the original SA. With queued packets this lets the clone splice and free skbs owned by the original IPTFS queue, leading to use-after-free and double-free reports in iptfs_destroy_state() and skb release paths. Reinitialize the clone's runtime state before publishing it through x->mode_data. Because clone_state() now publishes a destroyable mode_data object before init_state(), take the mode callback module reference there. Avoid taking it again from __iptfs_init_state() for the same object.
Quoted source text, attributed separately from HOL analysis.