CVE-2012-0217

HIGHCVSS v2 · 7.27.2—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.2 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:L/AC:L/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 37.2% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
7.2EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, public exploit)
CISA-KEV: Not listedEPSS PROB: 37%CVSS v2: 7.2Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · public exploitExposed: 0

A fix is available — apply it.

The x86-64 kernel system-call functionality in Xen 4.1.2 and earlier, as used in Citrix XenServer 6.0.2 and earlier and other products; Oracle Solaris 11 and earlier; illumos before r13724; Joyent SmartOS before 20120614T184600Z; FreeBSD before 9.0-RELEASE-p3; NetBSD 6.0 Beta and earlier; Microsoft Windows Server 2008 R2 and R2 SP1 and Windows 7 Gold and SP1; and possibly other operating systems, when running on an Intel processor, incorrectly uses the sysret path in cases where a certain address is not a canonical address, which allows local users to gain privileges via a crafted application. NOTE: because this issue is due to incorrect use of the Intel specification, it should have been split into separate identifiers; however, there was some value in preserving the original mapping of the multi-codebase coordinated-disclosure effort to a single identifier.

CVSS v2.0 (legacy)
7.2HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.2(low)
EG Risk
63(Track)
EG Risk 63/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 computed
Severity72% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
37%
EPSS %ILE
98%
KEV
Not listed

Published

June 12, 2012

Last Modified

April 29, 2026

References (46)

Vendor Advisories for CVE-2012-0217(1)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:2.6.18-308.8.2.el52012-06-12redhat
redhatkernel-0:2.6.18-238.39.1.el52012-06-12redhat

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

(6 across 5 ecosystems)
Debian:6.0(2)
PackageVulnerable rangeFixed inDependents
kfreebsd-88.1+dfsg-7.1, 8.1+dfsg-8, 8.1+dfsg-8+squeeze1, 8.1+dfsg-8+squeeze28.1+dfsg-8+squeeze3—
xen4.0.1-2, 4.0.1-4, 4.0.1-5, 4.0.1-5.14.0.1-5.2—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
xen—4.1.3~rc1+hg-20120614.a9c0a89c08f2-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
xen—4.1.3~rc1+hg-20120614.a9c0a89c08f2-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
xen—4.1.3~rc1+hg-20120614.a9c0a89c08f2-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
xen—4.1.3~rc1+hg-20120614.a9c0a89c08f2-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 4× in last 7d / 14× 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 102 total refreshes for this CVE.

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

Publicly available exploits

(4 references)

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

  • Exploit-DBEDB-46508✓ verified
    First seen Mar 7, 2019

    FreeBSD - Intel SYSRET Privilege Escalation (Metasploit)

    Open source ↗
  • Exploit-DBEDB-28718✓ verified
    First seen Oct 4, 2013

    FreeBSD 9.0 - Intel SYSRET Kernel Privilege Escalation

    Open source ↗
  • Exploit-DBEDB-20861✓ verified
    First seen Aug 27, 2012

    Microsoft Windows Kernel - Intel x64 SYSRET (MS12-042)

    Open source ↗
  • Metasploitexploit/freebsd/local/intel_sysret_priv_esc✓ verified
    First seen Jun 12, 2012

    FreeBSD Intel SYSRET Privilege Escalation

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(4)

What is CVE-2012-0217?
CVE-2012-0217 is a high vulnerability published on June 12, 2012. The x86-64 kernel system-call functionality in Xen 4.1.2 and earlier, as used in Citrix XenServer 6.0.2 and earlier and other products; Oracle Solaris 11 and earlier; illumos before r13724; Joyent SmartOS before 20120614T184600Z; FreeBSD before 9.0-RELEASE-p3; NetBSD 6.0 Beta and earlier; Microsoft…
When was CVE-2012-0217 disclosed?
CVE-2012-0217 was first published in the National Vulnerability Database on June 12, 2012, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2012-0217 actively exploited?
CVE-2012-0217 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 37% probability of exploitation in the next 30 days, which ranks it in the top 1.6% of all scored CVEs.
How do I remediate CVE-2012-0217?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2012-0217, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2012-0217

Explore →

Is Your Infrastructure Affected by CVE-2012-0217?

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

Start Free Scan →Browse All CVEs