Answer in brief
CVE-2026-53240 records a High severity (CVSS 8.8) vulnerability in xfrm: iptfs: fix use-after-free on first_skb in __input_process_payload. 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 8.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 | >=3f3339885fb343b7b42d7c34717108ce07da24ae <8d9a79fbf5172d9c4c0146057af2360913265a11 || >=3f3339885fb343b7b42d7c34717108ce07da24ae <ff2ee35b6ce5fa8a8e24ea50b15733d5c8780198 || >=3f3339885fb343b7b42d7c34717108ce07da24ae <eb48730bb827d1550401a5d391903f9d90b493c8 | 8d9a79fbf5172d9c4c0146057af2360913265a11, ff2ee35b6ce5fa8a8e24ea50b15733d5c8780198, eb48730bb827d1550401a5d391903f9d90b493c8 |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
In the Linux kernel, the following vulnerability has been resolved: xfrm: iptfs: fix use-after-free on first_skb in __input_process_payload __input_process_payload() stores first_skb into xtfs->ra_newskb under drop_lock when starting partial reassembly, then unlocks and breaks out of the processing loop. The post-loop check reads xtfs->ra_newskb without the lock to decide whether first_skb is still owned: if (first_skb && first_iplen && !defer && first_skb != xtfs->ra_newskb) Between spin_unlock and this read, a concurrent CPU running iptfs_reassem_cont() (or the drop_timer hrtimer) can complete reassembly, NULL xtfs->ra_newskb, and free the skb. The check then evaluates first_skb != NULL as true, and pskb_trim/ip_summed/consume_skb operate on the freed skb — a use-after-free in skbuff_head_cache. Replace the unlocked read with a local bool that records whether first_skb was handed to the reassembly state in the current call. The flag is set after the existing spin_unlock, before the break, using the pointer equality that is stable at that point (first_skb == skb iff first_skb was stored in ra_newskb).
Quoted source text, attributed separately from HOL analysis.