Skip to content
Fencer Vulns
medium 4.7

CVE-2007-5906 json

Xen 3.1.1 allows virtual guest system users to cause a denial of service (hypervisor crash) by using a debug register (DR7) to set certain…

published 2007-11-09 18 y ago modified 2026-06-16 4 mo ago also EUVD-2007-5876

cvss
4.7
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 25%
public exploits
0
none known

Summary

Xen 3.1.1 allows virtual guest system users to cause a denial of service (hypervisor crash) by using a debug register (DR7) to set certain breakpoints.

Patch / fix

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

red hat advisories RHBA-2008:0314

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-5906 updated

kernel-xen 3.1.1 virtual guest system denial of service (hypervisor crash) possibility

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

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.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

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.