Menu

Star on GitHub · 3.2k

CVE-2026-31663

7.8 · HIGH

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() immed…

Published Apr 24, 2026CWE-826EPSS 0.13%

Overview

CVE-2026-31663 is a high-severity vulnerability. It was published on April 24, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-31663?

CVE-2026-31663 is a high-severity vulnerability. It was published on April 24, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-31663?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-31663?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-31663?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-31663 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all