CVE-2026-31663
HighIn 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.
CVSS 3.1 score
7.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness type
CWE-826CVE-2026-31663 is classified as CWE-826
See CWE-826 on MITRE CWE for full details on this weakness type.
Affected versions
Linux kernel versions
3.2.100,
3.16.55,
4.14.24,
4.15
and later are affected. Fixed in
6.12.94,
6.18.23,
6.19.13,
7.0
and their respective stable series.
References
7 total-
Patch
-
Patch
-
Patch
-
-
Frequently asked questions
-
What is CVE-2026-31663?
CVE-2026-31663 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 . It affects Linux kernel versions from 3.2.100 onward and has been patched in 6.12.94, 6.18.23, 6.19.13 and others. CVE-2026-31663 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2026-31663?
CVE-2026-31663 has a CVSS score of 7.8 out of 10, rated High severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. -
Is there a patch available for CVE-2026-31663?
Yes. CVE-2026-31663 has been patched. Fixed versions include 6.12.94, 6.18.23, 6.19.13 and others. If you are running Linux kernel 3.2.100 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-31663 actively exploited?
No. CVE-2026-31663 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.