Skip to content
Fencer Vulns
low 2.1

CVE-2007-6207 json

Xen 3.x, possibly before 3.1.2, when running on IA64 systems, does not check the RID value for mov_to_rr, which allows a VTi domain to read…

published 2007-12-04 18 y ago modified 2026-06-16 4 mo ago also EUVD-2007-6175

cvss
2.1
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

Summary

Xen 3.x, possibly before 3.1.2, when running on IA64 systems, does not check the RID value for mov_to_rr, which allows a VTi domain to read memory of other domains.

Patch / fix

  • kernel RHEL 5 2.6.18-53.1.14.el5
  • kernel-PAE RHEL 5 2.6.18-53.1.14.el5
  • kernel-xen RHEL 5 2.6.18-53.1.14.el5
  • kernel-kdump RHEL 5 2.6.18-53.1.14.el5
  • kernel-debuginfo-common RHEL 5 2.6.18-53.1.14.el5

red hat advisories RHSA-2008:0154

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2007-6207 updated

Security: some HVM domain can access another domain memory.

  • Red Hat Enterprise Linux (v. 5 server) kernel 2.6.18-53.1.14.el5, kernel-PAE 2.6.18-53.1.14.el5, kernel-xen 2.6.18-53.1.14.el5, kernel-kdump 2.6.18-53.1.14.el5, kernel-debuginfo-common 2.6.18-53.1.14.el5 Red Hat Enterprise Linux Desktop (v. 5 client) kernel 2.6.18-53.1.14.el5, kernel-PAE 2.6.18-53.1.14.el5, kernel-xen 2.6.18-53.1.14.el5, kernel-kdump 2.6.18-53.1.14.el5, kernel-debuginfo-common 2.6.18-53.1.14.el5
    fixed: vendor fix RHSA-2008:0154

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.