CVE-2026-92489

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-17. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

In the Linux kernel, the following vulnerability has been resolved:

xfrm: Fix skb double-free in xfrm_dev_direct_output()

A return value other than 1 from local_out() means that the skb has been consumed or its ownership was transferred. xfrm_dev_direct_output() nevertheless frees the skb on this path, causing a double-free when netfilter drops the packet and invalidating any other owner.

Return the local_out() result directly, matching the ownership handling in xfrm_output_resume().

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
49
EG Risk 49/100CISA SSVC

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
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (5)

Auto-updated Oct 2, 2026
No patch confirmed yet.
generic

xfrm: Fix skb double-free in xfrm_dev_direct_output() - kernel/git/stable/linux.git - Linux kernel stable tree

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

xfrm: Fix skb double-free in xfrm_dev_direct_output() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/621871b696b108026bf4b44ed4085ffa2102f417
generic

xfrm: Fix skb double-free in xfrm_dev_direct_output() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/56a347950e661c1a7f8f31c43a2ea53c2323b6f4
generic

xfrm: Fix skb double-free in xfrm_dev_direct_output() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2aed51fc58d9ce450e2c116efb956160fd06fa02
generic

xfrm: Fix skb double-free in xfrm_dev_direct_output() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/02deb637e965950148752a304dd1471212dd6470

Vendor Advisories for CVE-2026-92489(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-92489?
CVE-2026-92489 is a critical vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: xfrm: Fix skb double-free in xfrmdevdirect_output() A return value other than 1 from local_out() means that the skb has been consumed or its ownership was transferred. xfrmdevdirect_output() nevertheless frees the skb on this path,…
When was CVE-2026-92489 disclosed?
CVE-2026-92489 was first published on September 17, 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-92489 actively exploited?
CVE-2026-92489 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92489?
CVE-2026-92489 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-92489?
No fix for CVE-2026-92489 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-92489 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-92489?

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