CVE-2017-7228
🗓️ 04 Apr 2017 14:00:00Reported by mitreType 
cve🔗 web.nvd.nist.gov📰️ 2 Media mentions👁 118 Views🌐 WEB
| Reporter | Title | Published | Views | Family All 66 |
|---|---|---|---|---|
 | Xen - Broken Check in memory_exchange() Permits PV Guest Breakout Vulnerability | 12 Apr 201700:00 | – | zdt |
 | xen-kernel -- broken check in memory_exchange() permits PV guest breakout | 4 Apr 201700:00 | – | freebsd |
 | Xen Hypervisor Memory Disclosure | 30 Jun 201700:00 | – | bdu_fstec |
 | CVE-2017-7228 | 11 Apr 201700:00 | – | circl |
 | Citrix XenServer multiple vulnerabilities (CTX222565) | 14 Apr 201700:00 | – | nessus |
| Debian DLA-907-1 : xen security update | 24 Apr 201700:00 | – | nessus |
| Debian DSA-3847-1 : xen - security update | 10 May 201700:00 | – | nessus |
| Fedora 24 : xen (2017-03dc811be6) | 17 Apr 201700:00 | – | nessus |
| Fedora 25 : xen (2017-054729ab08) | 10 Apr 201700:00 | – | nessus |
| FreeBSD : xen-kernel -- broken check in memory_exchange() permits PV guest breakout (90becf7c-1acf-11e7-970f-002590263bf5) | 7 Apr 201700:00 | – | nessus |
10
| Parameter | Position | Path | Description | CWE |
|---|---|---|---|---|
| exch.in.extent_start | hypercall | memory_exchange() | A vulnerability in the memory_exchange() hypercall handler allows a PV guest kernel to write to an arbitrary virtual address with hypervisor privileges. The issue arises because the hypervisor uses guest_handle_okay() which only validates the start address, but the handler accesses memory using the exch.nr_exchanged offset without sufficient bounds checking. | CWE-129 |
| exch.in.nr_extents | hypercall | memory_exchange() | A vulnerability in the memory_exchange() hypercall handler allows a PV guest kernel to write to an arbitrary virtual address with hypervisor privileges. The issue arises because the hypervisor uses guest_handle_okay() which only validates the start address, but the handler accesses memory using the exch.nr_exchanged offset without sufficient bounds checking. | CWE-129 |
| exch.out.extent_start | hypercall | memory_exchange() | A vulnerability in the memory_exchange() hypercall handler allows a PV guest kernel to write to an arbitrary virtual address with hypervisor privileges. The issue arises because the hypervisor uses guest_handle_okay() which only validates the start address, but the handler accesses memory using the exch.nr_exchanged offset without sufficient bounds checking. | CWE-129 |
| exch.out.nr_extents | hypercall | memory_exchange() | A vulnerability in the memory_exchange() hypercall handler allows a PV guest kernel to write to an arbitrary virtual address with hypervisor privileges. The issue arises because the hypervisor uses guest_handle_okay() which only validates the start address, but the handler accesses memory using the exch.nr_exchanged offset without sufficient bounds checking. | CWE-129 |
| exch.nr_exchanged | hypercall | memory_exchange() | A vulnerability in the memory_exchange() hypercall handler allows a PV guest kernel to write to an arbitrary virtual address with hypervisor privileges. The issue arises because the hypervisor uses guest_handle_okay() which only validates the start address, but the handler accesses memory using the exch.nr_exchanged offset without sufficient bounds checking. | CWE-129 |
Data
Build on a solid foundation with Vulners data
We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data
Api
Power your application with Vulners API
The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access
App
Assess and manage vulnerabilities with Vulners tools
Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation
17 Jun 2026 01:23Current
6.3Medium risk
Vulners AI Score6.3
CVSS 27.2
CVSS 38.2
EPSS0.01569