Answer in brief
CVE-2026-31663 records a High severity (CVSS 7.8) vulnerability in xfrm: hold dev ref until after transport_finish NF_HOOK. 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.
Answer in brief
CVE-2026-31663 records a High severity (CVSS 7.8) vulnerability in xfrm: hold dev ref until after transport_finish NF_HOOK. 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 | >=acf568ee859f098279eadf551612f103afdacb4e <4236c30b437b80f673b9e08c8fae38b8d471ac9e || >=acf568ee859f098279eadf551612f103afdacb4e <0f451b43c88bf2b9c038b414be580efee42e031b || >=acf568ee859f098279eadf551612f103afdacb4e <5002beda5cac69d522dc54da0d5d463ed9c963d2 || >=acf568ee859f098279eadf551612f103afdacb4e <1c428b03840094410c5fb6a5db30640486bbbfcb || 69895c5ea0ca2e8d7de1e6d36965d0ab9730787f || 833760100588acfb267dac4d6a02ab9931237739 || e095ecaec6d94aa2156cceb98a85d409b51190f3 || >=3.2.100 <3.3 || >=3.16.55 <3.17 || >=4.14.24 <4.15 | 4236c30b437b80f673b9e08c8fae38b8d471ac9e, 0f451b43c88bf2b9c038b414be580efee42e031b, 5002beda5cac69d522dc54da0d5d463ed9c963d2, 1c428b03840094410c5fb6a5db30640486bbbfcb, 3.3, 3.17, 4.15 |
| Linux/Linuxgeneric | 4.15 | Not reported |
Published upstream
Apr 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
In the Linux kernel, the following vulnerability has been resolved: xfrm: hold dev ref until after transport_finish NF_HOOK After async crypto completes, xfrm_input_resume() calls dev_put() immediately on re-entry before the skb reaches transport_finish. The skb->dev pointer is then used inside NF_HOOK and its okfn, which can race with device teardown. Remove the dev_put from the async resumption entry and instead drop the reference after the NF_HOOK call in transport_finish, using a saved device pointer since NF_HOOK may consume the skb. This covers NF_DROP, NF_QUEUE and NF_STOLEN paths that skip the okfn. For non-transport exits (decaps, gro, drop) and secondary async return points, release the reference inline when async is set.
Quoted source text, attributed separately from HOL analysis.
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 | >=acf568ee859f098279eadf551612f103afdacb4e <4236c30b437b80f673b9e08c8fae38b8d471ac9e || >=acf568ee859f098279eadf551612f103afdacb4e <0f451b43c88bf2b9c038b414be580efee42e031b || >=acf568ee859f098279eadf551612f103afdacb4e <5002beda5cac69d522dc54da0d5d463ed9c963d2 || >=acf568ee859f098279eadf551612f103afdacb4e <1c428b03840094410c5fb6a5db30640486bbbfcb || 69895c5ea0ca2e8d7de1e6d36965d0ab9730787f || 833760100588acfb267dac4d6a02ab9931237739 || e095ecaec6d94aa2156cceb98a85d409b51190f3 || >=3.2.100 <3.3 || >=3.16.55 <3.17 || >=4.14.24 <4.15 | 4236c30b437b80f673b9e08c8fae38b8d471ac9e, 0f451b43c88bf2b9c038b414be580efee42e031b, 5002beda5cac69d522dc54da0d5d463ed9c963d2, 1c428b03840094410c5fb6a5db30640486bbbfcb, 3.3, 3.17, 4.15 |
| Linux/Linuxgeneric | 4.15 | Not reported |
Published upstream
Apr 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
In the Linux kernel, the following vulnerability has been resolved: xfrm: hold dev ref until after transport_finish NF_HOOK After async crypto completes, xfrm_input_resume() calls dev_put() immediately on re-entry before the skb reaches transport_finish. The skb->dev pointer is then used inside NF_HOOK and its okfn, which can race with device teardown. Remove the dev_put from the async resumption entry and instead drop the reference after the NF_HOOK call in transport_finish, using a saved device pointer since NF_HOOK may consume the skb. This covers NF_DROP, NF_QUEUE and NF_STOLEN paths that skip the okfn. For non-transport exits (decaps, gro, drop) and secondary async return points, release the reference inline when async is set.
Quoted source text, attributed separately from HOL analysis.