CVE-2026-97417

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this week

Also known asEUVD-2026-86030 (ENISA EUVD) · GHSA-86rv-j9hx-pv73 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

netfilter: nf_conntrack: use get_unaligned_be32() in tcp_sack()

The timestamp-only fast path dereferences the option stream as *(__be32 *)ptr, which assumes 4-byte alignment that the TCP option stream does not guarantee. Use get_unaligned_be32() instead, which reads the value safely and already returns host byte order, so the htonl() on the comparison constant can be dropped.

This matches the existing get_unaligned_be32() use later in the same function.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 24, 2026

Last Modified

October 3, 2026

Advisory Details (3)

Auto-updated Sep 25, 2026
Patch available.
Web page

netfilter: nf_conntrack: use get_unaligned_be32() in tcp_sack() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d3bf9eae486490832bd08fd62ab0ac601f346bd4
Web page

netfilter: nf_conntrack: use get_unaligned_be32() in tcp_sack() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7ecfa46a536578a7ed335ddf31a854127268c27c
Web page

netfilter: nf_conntrack: use get_unaligned_be32() in tcp_sack() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4abc1af7ac209c066f4e5dd75cdd56876e5829a9

Patch Availability(27)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:4.18.0-477.179.1.el8_82026-11-20redhat
redhatkernel-0:4.18.0-305.219.1.el8_42026-11-19redhat
ubuntulinux-tools-raspi-nolpae (5.15.0.1113.111) @ jammy2026-11-14ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1071.78) @ noble2026-11-14ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1067.70.1) @ noble2026-11-14ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.202.174) @ jammy2026-11-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1070.70) @ jammy2026-11-14ubuntu
ubuntulinux-tools-realtime-hwe-26.04-edge (7.0.0-43.43.1) @ resolute2026-11-14ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2056.58) @ noble2026-11-14ubuntu
ubuntulinux-vmware-tools-6.8.0-1010 (6.8.0-1010.10) @ noble2026-11-14ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1071.78~22.04.1) @ jammy2026-11-14ubuntu
ubuntulinux-tools-nvidia-64k-6.8 (6.8.0-1067.70) @ noble2026-11-14ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-149.149~22.04.1) @ jammy2026-11-14ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-42.42) @ resolute2026-11-14ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1064.65) @ noble2026-11-14ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1020.21) @ resolute2026-11-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1039.40) @ noble2026-11-14ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1017.17) @ resolute2026-11-14ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1124.133) @ jammy2026-11-14ubuntu
redhatkernel-0:5.14.0-570.155.1.el9_62026-11-11redhat
redhatkernel-0:2.6.32-754.67.1.el62026-11-11redhat
redhatkernel-0:5.14.0-427.162.1.el9_42026-11-11redhat
redhatopenshift/ose-rhel-coreos-9:4.22.9.8.202610241758-02026-10-27redhat
redhatkernel-0:5.14.0-687.55.1.el9_82026-10-08redhat
redhatkernel-0:6.12.0-211.63.1.el10_22026-10-08redhat
redhatkernel-rt-0:4.18.0-553.171.1.rt7.512.el8_102026-10-05redhat
redhatkernel-0:4.18.0-553.171.1.el8_102026-10-05redhat

These rows come from Red Hat and Ubuntu. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (57 versions)
  • every version up to 6.1.190-1: fixed in 6.1.190-1
—
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 (180 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Additional Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 9× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 180 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 80 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 01:33 UTCEchelonGraph re-scored
  2. 2026-11-22 01:33 UTCVendor advisory
  3. 2026-11-22 01:33 UTCGHSA enrichmentGHSA-86rv-j9hx-pv73 · GitHub severity HIGH · GitHub CVSS 7.5
  4. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  5. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  6. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  7. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  8. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  9. 2026-11-16 16:53 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-11-15 17:04 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-11-14 23:39 UTCEchelonGraph re-scored
  12. 2026-11-14 23:39 UTCVendor advisory
  13. 2026-11-14 23:39 UTCGHSA enrichmentGHSA-86rv-j9hx-pv73 · GitHub severity HIGH · GitHub CVSS 7.5
  14. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  15. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  16. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  17. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  18. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  19. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  20. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  21. 2026-11-07 21:57 UTCEchelonGraph re-scored
  22. 2026-11-07 21:57 UTCVendor advisory
  23. 2026-11-07 21:57 UTCGHSA enrichmentGHSA-86rv-j9hx-pv73 · GitHub severity HIGH · GitHub CVSS 7.5
  24. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  25. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
Show 75 more
  1. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  2. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  3. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  4. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  5. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  6. 2026-10-31 20:16 UTCEchelonGraph re-scored
  7. 2026-10-31 20:16 UTCVendor advisory
  8. 2026-10-31 20:15 UTCGHSA enrichmentGHSA-86rv-j9hx-pv73 · GitHub severity HIGH · GitHub CVSS 7.5
  9. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  12. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  14. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  16. 2026-10-25 13:47 UTCEchelonGraph re-scored
  17. 2026-10-24 18:33 UTCEchelonGraph re-scored
  18. 2026-10-24 18:33 UTCVendor advisory
  19. 2026-10-24 18:33 UTCGHSA enrichmentGHSA-86rv-j9hx-pv73 · GitHub severity HIGH · GitHub CVSS 7.5
  20. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  21. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  22. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  23. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  24. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-10-20 06:28 UTCEchelonGraph re-scored
  26. 2026-10-20 06:28 UTCVendor advisory
  27. 2026-10-20 06:28 UTCGHSA enrichmentGHSA-86rv-j9hx-pv73 · GitHub severity HIGH · GitHub CVSS 7.5
  28. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  29. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  30. 2026-10-18 02:56 UTCEchelonGraph re-scored
  31. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  32. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  33. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  34. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  35. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  36. 2026-10-13 04:03 UTCEchelonGraph re-scored
  37. 2026-10-13 04:03 UTCVendor advisory
  38. 2026-10-13 04:03 UTCGHSA enrichmentGHSA-86rv-j9hx-pv73 · GitHub severity HIGH · GitHub CVSS 7.5
  39. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  40. 2026-10-12 14:40 UTCEchelonGraph re-scored
  41. 2026-10-12 03:48 UTCVendor advisory
  42. 2026-10-12 03:48 UTCGHSA enrichmentGHSA-86rv-j9hx-pv73 · GitHub severity HIGH · GitHub CVSS 7.5
  43. 2026-10-11 19:11 UTCEchelonGraph re-scored
  44. 2026-10-11 16:41 UTCVendor advisory
  45. 2026-10-11 16:41 UTCGHSA enrichmentGHSA-86rv-j9hx-pv73 · GitHub severity HIGH · GitHub CVSS 7.5
  46. 2026-10-11 16:26 UTCEchelonGraph re-scored
  47. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  48. 2026-10-11 13:38 UTCEchelonGraph re-scored
  49. 2026-10-11 05:45 UTCEchelonGraph re-scored
  50. 2026-10-11 05:45 UTCVendor advisory
  51. 2026-10-11 05:45 UTCGHSA enrichmentGHSA-86rv-j9hx-pv73 · GitHub severity HIGH · GitHub CVSS 7.5
  52. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  53. 2026-10-10 18:50 UTCVendor advisory
  54. 2026-10-10 18:50 UTCGHSA enrichmentGHSA-86rv-j9hx-pv73 · GitHub severity HIGH · GitHub CVSS 7.5
  55. 2026-10-10 07:55 UTCVendor advisory
  56. 2026-10-10 07:55 UTCGHSA enrichmentGHSA-86rv-j9hx-pv73 · GitHub severity HIGH · GitHub CVSS 7.5
  57. 2026-10-09 20:58 UTCEchelonGraph re-scored
  58. 2026-10-09 20:58 UTCVendor advisory
  59. 2026-10-09 20:58 UTCGHSA enrichmentGHSA-86rv-j9hx-pv73 · GitHub severity HIGH · GitHub CVSS 7.5
  60. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  61. 2026-10-09 10:03 UTCVendor advisory
  62. 2026-10-09 10:03 UTCGHSA enrichmentGHSA-86rv-j9hx-pv73 · GitHub severity HIGH · GitHub CVSS 7.5
  63. 2026-10-08 23:06 UTCEchelonGraph re-scored
  64. 2026-10-08 23:06 UTCVendor advisory
  65. 2026-10-08 23:06 UTCGHSA enrichmentGHSA-86rv-j9hx-pv73 · GitHub severity HIGH · GitHub CVSS 7.5
  66. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  67. 2026-10-08 12:11 UTCVendor advisory
  68. 2026-10-08 12:11 UTCGHSA enrichmentGHSA-86rv-j9hx-pv73 · GitHub severity HIGH · GitHub CVSS 7.5
  69. 2026-10-08 01:16 UTCEchelonGraph re-scored
  70. 2026-10-08 01:16 UTCVendor advisory
  71. 2026-10-08 01:16 UTCGHSA enrichmentGHSA-86rv-j9hx-pv73 · GitHub severity HIGH · GitHub CVSS 7.5
  72. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  73. 2026-10-07 14:19 UTCVendor advisory
  74. 2026-10-07 14:19 UTCGHSA enrichmentGHSA-86rv-j9hx-pv73 · GitHub severity HIGH · GitHub CVSS 7.5
  75. 2026-10-07 03:04 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-97417?
CVE-2026-97417 is a high-severity vulnerability; its CVE record was published on September 24, 2026. In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_conntrack: use get_unaligned_be32() in tcp_sack() The timestamp-only fast path dereferences the option stream as *(__be32 *)ptr, which assumes 4-byte alignment that the TCP option stream does not guarantee. Use…
When was the CVE record for CVE-2026-97417 published?
The CVE record for CVE-2026-97417 was published on September 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 3, 2026; the record at its source may have been updated since.
Is CVE-2026-97417 actively exploited?
CVE-2026-97417 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97417?
CVE-2026-97417 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97417?
A fix for CVE-2026-97417 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-97417 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-97417

Explore →

Is Your Infrastructure Affected by CVE-2026-97417?

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