CVE-2026-31663

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-24. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

April 24, 2026

Last Modified

September 18, 2026

Advisory Details (3)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

xfrm: hold dev ref until after transport_finish NF_HOOK - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5002beda5cac69d522dc54da0d5d463ed9c963d2
generic

xfrm: hold dev ref until after transport_finish NF_HOOK - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1c428b03840094410c5fb6a5db30640486bbbfcb
generic

xfrm: hold dev ref until after transport_finish NF_HOOK - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0f451b43c88bf2b9c038b414be580efee42e031b

Vendor Advisories for CVE-2026-31663(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-09-18ubuntu
redhatkernel-0:5.14.0-687.49.1.el9_82026-09-17redhat
redhatkernel-0:4.18.0-553.164.1.el8_102026-09-17redhat
redhatkernel-rt-0:4.18.0-553.164.1.rt7.505.el8_102026-09-17redhat
redhatkernel-0:6.12.0-211.55.1.el10_22026-09-15redhat
linuxKernel @ 6.12.94—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (500 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (127 versions)6.19.13-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(5)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 25× in last 7d / 52× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 248 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-18 13:18 UTCEG score recompute
  4. 2026-09-18 13:18 UTCVendor advisory
  5. 2026-09-18 13:18 UTCGHSA enrichment
  6. 2026-09-18 12:20 UTCEG score recompute
  7. 2026-09-18 12:20 UTCVendor advisory
  8. 2026-09-18 12:20 UTCGHSA enrichment
  9. 2026-09-17 19:30 UTCEPSS rescore
  10. 2026-09-17 12:19 UTCEG score recompute
  11. 2026-09-17 12:19 UTCVendor advisory
  12. 2026-09-17 12:19 UTCGHSA enrichment
  13. 2026-09-17 12:11 UTCEG score recompute
  14. 2026-09-17 12:11 UTCVendor advisory
  15. 2026-09-17 12:11 UTCGHSA enrichment
  16. 2026-09-16 14:08 UTCEPSS rescore
  17. 2026-09-16 05:15 UTCEPSS rescore
  18. 2026-09-15 12:31 UTCEG score recompute
  19. 2026-09-15 12:31 UTCVendor advisory
  20. 2026-09-15 12:31 UTCGHSA enrichment
  21. 2026-09-15 12:14 UTCEG score recompute
  22. 2026-09-15 12:14 UTCVendor advisory
  23. 2026-09-15 12:14 UTCGHSA enrichment
  24. 2026-09-13 16:47 UTCEPSS rescore
  25. 2026-09-12 15:01 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 14:52 UTCEPSS rescore
  2. 2026-09-10 09:34 UTCEPSS rescore
  3. 2026-09-08 22:00 UTCEPSS rescore
  4. 2026-09-08 02:07 UTCOSV refresh
  5. 2026-09-07 16:01 UTCEPSS rescore
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-04 05:06 UTCEPSS rescore
  9. 2026-09-02 14:11 UTCEPSS rescore
  10. 2026-09-01 13:53 UTCEPSS rescore
  11. 2026-09-01 04:39 UTCEPSS rescore
  12. 2026-09-01 04:39 UTCEPSS rescore
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-27 14:25 UTCEPSS rescore
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-24 14:17 UTCEPSS rescore
  20. 2026-08-23 00:19 UTCEPSS rescore
  21. 2026-08-21 23:49 UTCEPSS rescore
  22. 2026-08-21 12:32 UTCEG score recompute
  23. 2026-08-21 12:32 UTCGHSA enrichment
  24. 2026-08-20 13:59 UTCEG score recompute
  25. 2026-08-20 13:59 UTCGHSA enrichment
  26. 2026-08-20 12:45 UTCEG score recompute
  27. 2026-08-20 12:45 UTCGHSA enrichment
  28. 2026-08-19 17:03 UTCEPSS rescore
  29. 2026-08-19 12:11 UTCEG score recompute
  30. 2026-08-19 12:11 UTCGHSA enrichment
  31. 2026-08-18 13:48 UTCEPSS rescore
  32. 2026-08-17 14:48 UTCEG score recompute
  33. 2026-08-17 14:48 UTCGHSA enrichment
  34. 2026-08-17 13:47 UTCEPSS rescore
  35. 2026-08-16 14:56 UTCEPSS rescore
  36. 2026-08-16 05:46 UTCEG score recompute
  37. 2026-08-16 05:46 UTCGHSA enrichment
  38. 2026-08-16 02:14 UTCEPSS rescore
  39. 2026-08-15 01:30 UTCEPSS rescore
  40. 2026-08-14 17:02 UTCGHSA enrichment
  41. 2026-08-14 04:06 UTCEG score recompute
  42. 2026-08-14 04:06 UTCGHSA enrichment
  43. 2026-08-13 22:00 UTCEPSS rescore
  44. 2026-08-13 08:31 UTCGHSA enrichment
  45. 2026-08-12 17:48 UTCEG score recompute
  46. 2026-08-12 17:48 UTCGHSA enrichment
  47. 2026-08-12 13:50 UTCEPSS rescore
  48. 2026-08-11 16:41 UTCEG score recompute
  49. 2026-08-11 16:41 UTCGHSA enrichment
  50. 2026-08-11 02:08 UTCEG score recompute
  51. 2026-08-11 02:08 UTCGHSA enrichment
  52. 2026-08-11 00:00 UTCEPSS rescore
  53. 2026-08-10 04:33 UTCGHSA enrichment
  54. 2026-08-09 15:56 UTCEG score recompute
  55. 2026-08-09 15:56 UTCGHSA enrichment
  56. 2026-08-09 13:46 UTCEPSS rescore
  57. 2026-08-09 03:18 UTCEG score recompute
  58. 2026-08-09 03:18 UTCGHSA enrichment
  59. 2026-08-08 16:37 UTCEPSS rescore
  60. 2026-08-08 01:10 UTCEG score recompute
  61. 2026-08-08 01:10 UTCGHSA enrichment
  62. 2026-08-07 12:32 UTCEG score recompute
  63. 2026-08-07 12:32 UTCGHSA enrichment
  64. 2026-08-06 13:46 UTCEPSS rescore
  65. 2026-08-06 13:39 UTCEG score recompute
  66. 2026-08-06 13:39 UTCGHSA enrichment
  67. 2026-08-06 12:34 UTCGHSA enrichment
  68. 2026-08-06 01:14 UTCEG score recompute
  69. 2026-08-06 01:14 UTCGHSA enrichment
  70. 2026-08-05 19:17 UTCEPSS rescore
  71. 2026-08-05 12:37 UTCEG score recompute
  72. 2026-08-05 12:37 UTCGHSA enrichment
  73. 2026-08-04 15:10 UTCEPSS rescore
  74. 2026-08-04 10:38 UTCEPSS rescore
  75. 2026-08-03 21:00 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-31663?
CVE-2026-31663 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: xfrm: hold dev ref until after transportfinish NFHOOK After async crypto completes, xfrminputresume() calls dev_put() immediately on re-entry before the skb reaches transport_finish. The skb->dev pointer is then used inside NF_HOOK…
When was CVE-2026-31663 disclosed?
CVE-2026-31663 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31663 actively exploited?
CVE-2026-31663 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.1% of all scored CVEs.
What is the CVSS score of CVE-2026-31663?
CVE-2026-31663 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31663?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31663, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31663

Explore →

Is Your Infrastructure Affected by CVE-2026-31663?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs