CVE-2017-5715

HIGHNVD 5.68.3▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.3 because EPSS predicts 74% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs). NVD baseline CVSS 5.6 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: epss, nvd
Weaponized
8.3EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 74%
  • Public exploit code is available (ssvc poc, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 74%CVSS: 5.6Exploit: ssvc poc · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is available — apply it.

Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis.

CVSS v3
5.6
EG Score
8.3HIGHhigh confidence
EG Risk
67
EG Risk 67/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
Severity83% × 45%
Exploitation74% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
74%
EPSS %ILE
99th
KEV
Not listed

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

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

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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

January 4, 2018

Last Modified

May 6, 2025

References (188)

Vendor Advisories for CVE-2017-5715(5)

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

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-image-generic-lts-trusty (3.13.0.140.131) @ precise2026-05-28ubuntu
ubuntulinux-image-extra-4.13.0-36-generic (4.13.0-36.40~16.04.1) @ xenial2026-05-28ubuntu
ubuntulibwebkit2gtk-4.0-37 (2.18.5-0ubuntu0.17.04.1) @ zesty2026-05-28ubuntu
ubuntulinux-image-extra-3.13.0-143-generic (3.13.0-143.192) @ trusty2026-05-28ubuntu
ubuntulinux-image-3.2.0-133-generic (3.2.0-133.179) @ precise2026-05-28ubuntu
ubuntulinux-image-extra-4.4.0-9023-euclid (4.4.0-9023.24) @ xenial2026-05-28ubuntu
ubuntulinux-image-extra-4.13.0-31-generic (4.13.0-31.34~16.04.1) @ xenial2026-05-28ubuntu
redhatkernel-alt-0:4.14.0-49.8.1.el7a2018-06-26redhat
redhatkernel-0:2.6.32-696.28.1.el62018-05-08redhat
redhatkernel-0:2.6.32-573.55.2.el62018-05-08redhat
redhatkernel-0:2.6.18-348.39.1.el52018-04-25redhat
redhatkernel-0:3.10.0-327.66.1.el72018-04-24redhat
redhatkernel-0:2.6.18-430.el52018-04-23redhat
redhatkernel-0:3.10.0-693.25.2.el72018-04-17redhat
redhatkernel-0:3.10.0-514.48.1.el72018-04-17redhat
redhatlibvirt-0:3.9.0-14.el72018-04-10redhat
redhatkernel-0:3.10.0-862.el72018-04-10redhat
redhatlinux-firmware-0:20180220-62.git6d51311.el72018-04-10redhat
redhatmicrocode_ctl-2:2.1-29.el72018-04-10redhat
redhatqemu-kvm-ma-10:2.10.0-21.el72018-04-10redhat
redhatkernel-rt-1:3.10.0-693.11.1.rt56.606.el6rt2018-01-04redhat
redhatdracut-0:033-502.el7_4.12018-01-04redhat
redhatqemu-kvm-10:1.5.3-126.el7_3.132018-01-04redhat
redhatqemu-kvm-10:1.5.3-141.el7_4.62018-01-04redhat
redhatkernel-0:2.6.32-358.84.2.el62018-01-04redhat
redhatqemu-kvm-rhev-10:2.6.0-28.el7_3.152018-01-04redhat
redhatkernel-rt-0:3.10.0-693.11.1.rt56.639.el72018-01-04redhat
redhatkernel-0:2.6.32-431.85.2.el62018-01-04redhat
redhatkernel-0:2.6.32-504.64.4.el62018-01-04redhat
redhatkernel-0:2.6.32-220.76.2.el62018-01-04redhat

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

(34 across 9 ecosystems)
Debian:11(6)
PackageVulnerable rangeFix by version rangeDependents
amd64-microcode0.20120117-1 ... 3.20171205.2 (25 versions)
  • every version up to 3.20180515.1: fixed in 3.20180515.1
—
intel-microcode0.20080131-1 ... 3.20180425.1~deb9u1 (95 versions)
  • every version up to 3.20180425.1: fixed in 3.20180425.1
—
linux—
  • every version up to 4.15.11-1: fixed in 4.15.11-1
—
nvidia-graphics-drivers1.0.6629+1-2 ... 384.98-3~bpo9+1 (350 versions)
  • every version up to 384.111-1: fixed in 384.111-1
—
qemu—
  • every version up to 1:2.12~rc3+dfsg-1: fixed in 1:2.12~rc3+dfsg-1
—
xen—
  • every version up to 4.11.1~pre+1.733450b39b-1: fixed in 4.11.1~pre+1.733450b39b-1
—
Debian:12(6)
PackageVulnerable rangeFix by version rangeDependents
amd64-microcode0.20120117-1 ... 3.20171205.2 (25 versions)
  • every version up to 3.20180515.1: fixed in 3.20180515.1
—
intel-microcode0.20080131-1 ... 3.20180425.1~deb9u1 (95 versions)
  • every version up to 3.20180425.1: fixed in 3.20180425.1
—
linux—
  • every version up to 4.15.11-1: fixed in 4.15.11-1
—
nvidia-graphics-drivers1.0.6629+1-2 ... 384.98-3~bpo9+1 (350 versions)
  • every version up to 384.111-1: fixed in 384.111-1
—
qemu—
  • every version up to 1:2.12~rc3+dfsg-1: fixed in 1:2.12~rc3+dfsg-1
—
xen—
  • every version up to 4.11.1~pre+1.733450b39b-1: fixed in 4.11.1~pre+1.733450b39b-1
—
Debian:13(6)
PackageVulnerable rangeFix by version rangeDependents
amd64-microcode0.20120117-1 ... 3.20171205.2 (25 versions)
  • every version up to 3.20180515.1: fixed in 3.20180515.1
—
intel-microcode0.20080131-1 ... 3.20180425.1~deb9u1 (95 versions)
  • every version up to 3.20180425.1: fixed in 3.20180425.1
—
linux—
  • every version up to 4.15.11-1: fixed in 4.15.11-1
—
nvidia-graphics-drivers1.0.6629+1-2 ... 384.98-3~bpo9+1 (350 versions)
  • every version up to 384.111-1: fixed in 384.111-1
—
qemu—
  • every version up to 1:2.12~rc3+dfsg-1: fixed in 1:2.12~rc3+dfsg-1
—
xen—
  • every version up to 4.11.1~pre+1.733450b39b-1: fixed in 4.11.1~pre+1.733450b39b-1
—
Debian:14(6)
PackageVulnerable rangeFix by version rangeDependents
amd64-microcode0.20120117-1 ... 3.20171205.2 (25 versions)
  • every version up to 3.20180515.1: fixed in 3.20180515.1
—
intel-microcode0.20080131-1 ... 3.20180425.1~deb9u1 (95 versions)
  • every version up to 3.20180425.1: fixed in 3.20180425.1
—
linux—
  • every version up to 4.15.11-1: fixed in 4.15.11-1
—
nvidia-graphics-drivers1.0.6629+1-2 ... 384.98-3~bpo9+1 (350 versions)
  • every version up to 384.111-1: fixed in 384.111-1
—
qemu—
  • every version up to 1:2.12~rc3+dfsg-1: fixed in 1:2.12~rc3+dfsg-1
—
xen—
  • every version up to 4.11.1~pre+1.733450b39b-1: fixed in 4.11.1~pre+1.733450b39b-1
—
Debian:9(4)
PackageVulnerable rangeFix by version rangeDependents
amd64-microcode0.20120117-1 ... 3.20181128.1~deb8u1 (30 versions)
  • every version up to 3.20181128.1~deb9u1: fixed in 3.20181128.1~deb9u1
—
linux4.9.30-2 ... 4.9.88-1~bpo8+1 (25 versions)
  • every version up to 4.9.88-1: fixed in 4.9.88-1
—
qemu1:2.8+dfsg-6, 1:2.8+dfsg-6+deb9u1, 1:2.8+dfsg-6+deb9u2, 1:2.8+dfsg-6+deb9u3
  • every version up to 1:2.8+dfsg-6+deb9u4: fixed in 1:2.8+dfsg-6+deb9u4
—
xen4.8.1-1+deb9u1 ... 4.8.3+comet2+shim4.10.0+comet3-1+deb9u5 (7 versions)
  • every version up to 4.8.3+xsa262+shim4.10.0+comet3-1+deb9u6: fixed in 4.8.3+xsa262+shim4.10.0+comet3-1+deb9u6
—
Debian:8(3)
PackageVulnerable rangeFix by version rangeDependents
amd64-microcode0.20120117-1 ... 3.20181128.1~bpo9+1 (29 versions)
  • every version up to 3.20181128.1~deb8u1: fixed in 3.20181128.1~deb8u1
—
linux3.16.36-1 ... 3.16.7-ckt9-3~deb8u1~bpo70+1 (56 versions)
  • every version up to 3.16.57-1: fixed in 3.16.57-1
  • every version up to 3.16.56-1: fixed in 3.16.56-1
—
qemu1:2.1+dfsg-11 ... 1:2.1+dfsg-12~bpo70+1 (12 versions)
  • every version up to 1:2.1+dfsg-12+deb8u7: fixed in 1:2.1+dfsg-12+deb8u7
—
Alpine:v3.5(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.7.3-r4: fixed in 4.7.3-r4
—
Alpine:v3.6(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.8.2-r4: fixed in 4.8.2-r4
—
Debian:7(1)
PackageVulnerable rangeFix by version rangeDependents
linux3.2.41-2 ... 3.2.96-3 (71 versions)
  • every version up to 3.2.101-1: fixed in 3.2.101-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(22)

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 3× in last 7d / 12× 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.

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

Publicly available exploits

(3 references)

Working exploit code is in the public domain (2 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCmathse/meltdown-spectre-bios-list
    First seen Jan 14, 2018

    a list of BIOS/Firmware fixes adressing CVE-2017-5715, CVE-2017-5753, CVE-2017-5754

    Open source ↗
  • GitHub PoCopsxcq/exploit-cve-2017-5715
    First seen Jan 9, 2018

    Spectre exploit

    Open source ↗
  • Exploit-DBEDB-43427
    First seen Jan 3, 2018

    Multiple CPUs - 'Spectre' Information Disclosure

    Open source ↗

Past incidents using this CVE

(1)

This CVE was central to one or more publicly-documented breaches. Each card links to authoritative reporting at the time of the incident.

  • Spectre & Meltdown (CPU side-channel)Jan 2018

    Speculative-execution side-channel attacks against virtually every modern CPU (Intel, AMD, ARM). Required hardware-firmware updates and OS kernel changes across the industry.

    Source: ZDNet

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2017-5715?
CVE-2017-5715 is a high vulnerability published on January 4, 2018. Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis.
When was CVE-2017-5715 disclosed?
CVE-2017-5715 was first published on January 4, 2018, with the most recent update on May 6, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-5715 actively exploited?
CVE-2017-5715 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 74% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-5715?
CVE-2017-5715 has a CVSS v3 base score of 5.6 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.3 (HIGH).
How do I remediate CVE-2017-5715?
A fix for CVE-2017-5715 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2017-5715 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-2017-5715

Explore →

Is Your Infrastructure Affected by CVE-2017-5715?

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

Book a Demo →Browse All CVEs