CVE-2017-14316

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-14. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A parameter verification issue was discovered in Xen through 4.9.x. The function alloc_heap_pages allows callers to specify the first NUMA node that should be used for allocations through the memflags parameter; the node is extracted using the MEMF_get_node macro. While the function checks to see if the special constant NUMA_NO_NODE is specified, it otherwise does not handle the case where node >= MAX_NUMNODES. This allows an out-of-bounds access to an internal array.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
44
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 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 12, 2017

Last Modified

June 17, 2026

Advisory Details (6)

Auto-updated Aug 31, 2026
Patch available.
genericMentions a patch (unverified)

[SECURITY] [DLA 1549-1] xen security update

https://lists.debian.org/debian-lts-announce/2018/10/msg00009.html
generic

XSA-231 - Xen Security Advisories

http://xenbits.xen.org/xsa/advisory-231.html
generic
http://www.securitytracker.com/id/1039348
generic

CVE-2017-14316 - PSIRT.COM

http://www.securityfocus.com/bid/100818
generic

[SECURITY] [DSA 4050-1] xen security update

https://www.debian.org/security/2017/dsa-4050
generic

Loading...

https://support.citrix.com/article/CTX227185

Affected Packages

(29 across 29 ecosystems)
Alpine:v3.10(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.9.0-r4: fixed in 4.9.0-r4
—
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.9.0-r4: fixed in 4.9.0-r4
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.9.0-r4: fixed in 4.9.0-r4
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.9.0-r4: fixed in 4.9.0-r4
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.9.0-r4: fixed in 4.9.0-r4
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.9.0-r4: fixed in 4.9.0-r4
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.9.0-r4: fixed in 4.9.0-r4
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.9.0-r4: fixed in 4.9.0-r4
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.9.0-r4: fixed in 4.9.0-r4
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.9.0-r4: fixed in 4.9.0-r4
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.9.0-r4: fixed in 4.9.0-r4
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.9.0-r4: fixed in 4.9.0-r4
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.9.0-r4: fixed in 4.9.0-r4
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.9.0-r4: fixed in 4.9.0-r4
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.9.0-r4: fixed in 4.9.0-r4
—
Alpine:v3.3(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.6.3-r9: fixed in 4.6.3-r9
—
Alpine:v3.4(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.6.3-r11: fixed in 4.6.3-r11
—
Alpine:v3.5(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.7.2-r2: fixed in 4.7.2-r2
—
Alpine:v3.6(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.8.2-r1: fixed in 4.8.2-r1
—
Alpine:v3.7(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.9.0-r4: fixed in 4.9.0-r4
—
Alpine:v3.8(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.9.0-r4: fixed in 4.9.0-r4
—
Alpine:v3.9(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.9.0-r4: fixed in 4.9.0-r4
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.8.2+xsa245-0+deb9u1: fixed in 4.8.2+xsa245-0+deb9u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.8.2+xsa245-0+deb9u1: fixed in 4.8.2+xsa245-0+deb9u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.8.2+xsa245-0+deb9u1: fixed in 4.8.2+xsa245-0+deb9u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.8.2+xsa245-0+deb9u1: fixed in 4.8.2+xsa245-0+deb9u1
—
Debian:7(1)
PackageVulnerable rangeFix by version rangeDependents
xen4.1.4-3 ... 4.1.6.lts1-8 (20 versions)
  • every version up to 4.1.6.lts1-9: fixed in 4.1.6.lts1-9
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
xen4.4.1-9 ... 4.4.4lts1-0+deb8u1 (12 versions)
  • every version up to 4.4.4lts2-0+deb8u1: fixed in 4.4.4lts2-0+deb8u1
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
xen4.8.1-1+deb9u1, 4.8.1-1+deb9u2, 4.8.1-1+deb9u3
  • every version up to 4.8.2+xsa245-0+deb9u1: fixed in 4.8.2+xsa245-0+deb9u1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× 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 159 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2017-14316?
CVE-2017-14316 is a high vulnerability published on September 12, 2017. A parameter verification issue was discovered in Xen through 4.9.x. The function allocheappages allows callers to specify the first NUMA node that should be used for allocations through the memflags parameter; the node is extracted using the MEMFgetnode macro. While the function checks to see if…
When was CVE-2017-14316 disclosed?
CVE-2017-14316 was first published on September 12, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-14316 actively exploited?
CVE-2017-14316 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-14316?
CVE-2017-14316 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2017-14316?
A fix for CVE-2017-14316 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-14316

Explore →

Is Your Infrastructure Affected by CVE-2017-14316?

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

Book a Demo →Browse All CVEs