CVE-2026-63911

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated 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: iptfs: reset runtime state when cloning SAs

iptfs_clone_state() clones the IPTFS mode data with kmemdup(). This copies runtime objects which must not be shared with the original SA, including the embedded sk_buff_head, hrtimers, spinlock, and in-flight reassembly/reorder state.

If xfrm_state_migrate() fails after clone_state() but before the later init_state() call has reinitialized those fields, the cloned state can be destroyed by xfrm_state_gc_task() with list and timer state copied from the original SA. With queued packets this lets the clone splice and free skbs owned by the original IPTFS queue, leading to use-after-free and double-free reports in iptfs_destroy_state() and skb release paths.

Reinitialize the clone's runtime state before publishing it through x->mode_data. Because clone_state() now publishes a destroyable mode_data object before init_state(), take the mode callback module reference there. Avoid taking it again from __iptfs_init_state() for the same object.

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
6%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

xfrm: iptfs: reset runtime state when cloning SAs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dfb9f6cbfa9826655a49698cf90eb800fce2178e
generic

xfrm: iptfs: reset runtime state when cloning SAs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9327252e04626d4bb02ca8c0c108fbe8eabf0c5a
generic

xfrm: iptfs: reset runtime state when cloning SAs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7f83d174073234839aea176f265e517e0d50a1d2

Vendor Advisories for CVE-2026-63911(1)

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

Patch Availability(5)

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 33× in last 7d / 163× 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 208 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-63911?
CVE-2026-63911 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: xfrm: iptfs: reset runtime state when cloning SAs iptfsclonestate() clones the IPTFS mode data with kmemdup(). This copies runtime objects which must not be shared with the original SA, including the embedded skbuffhead, hrtimers,…
When was CVE-2026-63911 disclosed?
CVE-2026-63911 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63911 actively exploited?
CVE-2026-63911 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 94.2% of all scored CVEs.
What is the CVSS score of CVE-2026-63911?
CVE-2026-63911 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63911?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63911, 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-63911

Explore →

Is Your Infrastructure Affected by CVE-2026-63911?

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