The ip6gre_err function in net/ipv6/ip6_gre.c in the Linux kernel allows remote attackers to have unspecified impact via vectors involving GRE flags in an IPv6 packet, which trigger an out-of-bounds access.
CVE-2017-5897
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-14. NVD baseline CVSS 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.8
- EG Score
- 9.8(medium)
- EG Risk
- 51(Track)EG Risk 51/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 computedSeverity98% × 45%Exploitation5% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 5%
- EPSS %ILE
- 91%
- KEV
- Not listed
Published
March 23, 2017
Last Modified
June 17, 2026
Advisory Details (6)
Auto-updated Aug 17, 2026oss-security - Re: CVE Request: Linux: ip6_gre: invalid reads in ip6gre_err()
http://www.openwall.com/lists/oss-security/2017/02/07/2Android Security Bulletin—September 2017 | Android Open Source Project
https://source.android.com/security/bulletin/2017-09-01ip6_gre: fix ip6gre_err() invalid reads - kernel/git/netdev/net.git - Netdev Group's networking tree
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=7892032cfe67f4bde6fc2ee967e45a8fbaf33756Patch Availability(4)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | linux-image-extra-4.10.0-27-generic (4.10.0-27.30~16.04.2) @ xenial | 2026-05-20 | ubuntu |
| ubuntu | linux-image-extra-3.13.0-157-generic (3.13.0-157.207) @ trusty | 2026-05-20 | ubuntu |
| ubuntu | linux-image-extra-4.4.0-75-generic (4.4.0-75.96~14.04.1) @ trusty | 2026-05-20 | ubuntu |
| ubuntu | linux-image-extra-4.4.0-75-generic (4.4.0-75.96) @ xenial | 2026-05-20 | ubuntu |
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
(5 across 5 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| linux | — | 4.9.13-1 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| linux | — | 4.9.13-1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| linux | — | 4.9.13-1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| linux | — | 4.9.13-1 | — |
Debian:8(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| linux | 3.16.36-1 ... 3.16.7-ckt9-3~deb8u1~bpo70+1 (42 versions) | 3.16.39-1+deb8u1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(4)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 7× in last 7d / 23× 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 138 total refreshes for this CVE.
- 2026-08-20 22:51 UTCEPSS rescore
- 2026-08-19 16:59 UTCEPSS rescore
- 2026-08-18 13:43 UTCEPSS rescore
- 2026-08-17 13:42 UTCEPSS rescore
- 2026-08-16 14:51 UTCEPSS rescore
- 2026-08-16 02:10 UTCEPSS rescore
- 2026-08-15 01:26 UTCEPSS rescore
- 2026-08-12 13:46 UTCEPSS rescore
- 2026-08-10 03:39 UTCOSV refresh
- 2026-08-09 13:42 UTCEPSS rescore
- 2026-08-07 16:22 UTCEPSS rescore
- 2026-08-06 13:42 UTCEPSS rescore
- 2026-08-05 19:12 UTCEPSS rescore
- 2026-08-04 15:05 UTCEPSS rescore
- 2026-08-02 02:23 UTCEPSS rescore
- 2026-08-01 04:11 UTCEPSS rescore
- 2026-07-30 16:24 UTCEPSS rescore
- 2026-07-30 01:26 UTCEPSS rescore
- 2026-07-28 15:32 UTCEPSS rescore
- 2026-07-26 14:51 UTCEPSS rescore
- 2026-07-25 03:41 UTCOSV refresh
- 2026-07-23 14:15 UTCEPSS rescore
- 2026-07-23 01:30 UTCEG score recompute
- 2026-07-22 22:09 UTCEG score recompute
- 2026-07-22 14:04 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-07-22 14:04 UTCEPSS rescore
- 2026-07-21 15:21 UTCEPSS rescore
- 2026-07-21 15:21 UTCEPSS rescore
- 2026-07-20 17:04 UTCEPSS rescore
- 2026-07-19 14:28 UTCEPSS rescore
- 2026-07-19 14:28 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-18 10:00 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-15 16:54 UTCEPSS rescore
- 2026-07-15 01:56 UTCEPSS rescore
- 2026-07-15 01:56 UTCEPSS rescore
- 2026-07-13 22:26 UTCEPSS rescore
- 2026-07-12 05:43 UTCEPSS rescore
- 2026-07-11 08:24 UTCEPSS rescore
- 2026-07-09 19:06 UTCEPSS rescore
- 2026-07-08 15:10 UTCEPSS rescore
- 2026-07-07 22:42 UTCOSV refresh
- 2026-07-07 13:42 UTCEPSS rescore
- 2026-07-06 16:24 UTCEPSS rescore
- 2026-07-06 16:24 UTCEPSS rescore
- 2026-07-06 02:20 UTCEPSS rescore
- 2026-07-06 02:20 UTCEPSS rescore
- 2026-07-05 02:27 UTCEPSS rescore
- 2026-07-04 06:28 UTCEPSS rescore
- 2026-07-02 16:54 UTCEPSS rescore
- 2026-07-01 15:02 UTCEPSS rescore
- 2026-06-30 23:19 UTCEPSS rescore
- 2026-06-30 23:19 UTCEPSS rescore
- 2026-06-28 14:04 UTCEPSS rescore
- 2026-06-28 04:53 UTCEPSS rescore
- 2026-06-27 03:06 UTCEPSS rescore
- 2026-06-27 03:05 UTCEPSS rescore
- 2026-06-25 13:47 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-23 21:30 UTCEPSS rescore
- 2026-06-21 14:54 UTCEPSS rescore
- 2026-06-21 14:54 UTCEPSS rescore
- 2026-06-21 01:57 UTCEPSS rescore
- 2026-06-21 01:57 UTCEPSS rescore
- 2026-06-19 19:23 UTCEPSS rescore
- 2026-06-19 19:23 UTCEPSS rescore
- 2026-06-19 10:25 UTCOSV refresh
- 2026-06-18 17:50 UTCEPSS rescore
- 2026-06-17 17:50 UTCEPSS rescore
- 2026-06-16 17:50 UTCEPSS rescore
- 2026-06-16 17:50 UTCEPSS rescore
- 2026-06-15 17:45 UTCEPSS rescore
- 2026-06-14 23:14 UTCEPSS rescore
- 2026-06-13 22:57 UTCEPSS rescore
- 2026-06-12 23:09 UTCEPSS rescore
- 2026-06-10 22:15 UTCEPSS rescore
- 2026-06-10 13:19 UTCEPSS rescore
- 2026-06-08 14:14 UTCEPSS rescore
- 2026-06-08 14:14 UTCEPSS rescore
- 2026-06-07 15:22 UTCEPSS rescore
- 2026-06-07 15:22 UTCEPSS rescore
- 2026-06-06 13:45 UTCEPSS rescore
- 2026-06-06 13:45 UTCEPSS rescore
- 2026-06-05 22:44 UTCEPSS rescore
- 2026-06-05 06:08 UTCEPSS rescore
- 2026-06-05 06:08 UTCEPSS rescore
- 2026-06-04 13:10 UTCEPSS rescore
- 2026-06-02 20:11 UTCEPSS rescore
- 2026-06-02 20:11 UTCEPSS rescore
- 2026-06-01 13:49 UTCEPSS rescore
- 2026-05-31 22:28 UTCEPSS rescore
- 2026-05-31 22:28 UTCEPSS rescore
- 2026-05-31 00:14 UTCEPSS rescore
- 2026-05-31 00:14 UTCEPSS rescore
- 2026-05-30 19:23 UTCOSV refresh
- 2026-05-29 13:41 UTCEPSS rescore
Frequently asked(5)
What is CVE-2017-5897?
When was CVE-2017-5897 disclosed?
Is CVE-2017-5897 actively exploited?
What is the CVSS score of CVE-2017-5897?
How do I remediate CVE-2017-5897?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-5897
Is Your Infrastructure Affected by CVE-2017-5897?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.