The ssm_i emulation in Xen 5.1 on IA64 architectures allows attackers to cause a denial of service (dom0 panic) via certain traffic, as demo
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 70% of all records.
- Fixed version: kernel (Red Hat:enterprise_linux:5::client) 0:2.6.18-53.1.19.el5; kernel-debug (Red Hat:enterprise_linux:5::client) 0:2.6.18-53.1.19.el5; kernel-debug-debuginfo (Red Hat:enterprise_linux:5::client) 0:2.6.18-53.1.19.el5.
Low priority for now. Upgrade to kernel (Red Hat:enterprise_linux:5::client) 0:2.6.18-53.1.19.el5; kernel-debug (Red Hat:enterprise_linux:5::client) 0:2.6.18-53.1.19.el5; kernel-debug-debuginfo (Red Hat:enterprise_linux:5::client) 0:2.6.18-53.1.19.el5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
The ssm_i emulation in Xen 5.1 on IA64 architectures allows attackers to cause a denial of service (dom0 panic) via certain traffic, as demonstrated using an FTP stress test tool.
- Published
- Apr 2, 2008
- Updated
- Jun 16, 2026
- EPSS
- 1.3% · 70th percentile
- CWE
- —
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| xensource inc | xen | cpe:2.3:a:xensource_inc:xen |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- xensource inc xen5.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:enterprise_linux:5::client | kernel | before 0:2.6.18-53.1.19.el5 | 0:2.6.18-53.1.19.el5 |
| Red Hat:enterprise_linux:5::client | kernel-debug | before 0:2.6.18-53.1.19.el5 | 0:2.6.18-53.1.19.el5 |
| Red Hat:enterprise_linux:5::client | kernel-debug-debuginfo | before 0:2.6.18-53.1.19.el5 | 0:2.6.18-53.1.19.el5 |
| Red Hat:enterprise_linux:5::client | kernel-debug-devel | before 0:2.6.18-53.1.19.el5 | 0:2.6.18-53.1.19.el5 |
| Red Hat:enterprise_linux:5::client | kernel-debuginfo | before 0:2.6.18-53.1.19.el5 | 0:2.6.18-53.1.19.el5 |
| Red Hat:enterprise_linux:5::client | kernel-debuginfo-common | before 0:2.6.18-53.1.19.el5 | 0:2.6.18-53.1.19.el5 |
| Red Hat:enterprise_linux:5::client | kernel-devel | before 0:2.6.18-53.1.19.el5 | 0:2.6.18-53.1.19.el5 |
| Red Hat:enterprise_linux:5::client | kernel-doc | before 0:2.6.18-53.1.19.el5 | 0:2.6.18-53.1.19.el5 |
| Red Hat:enterprise_linux:5::client | kernel-headers | before 0:2.6.18-53.1.19.el5 | 0:2.6.18-53.1.19.el5 |
| Red Hat:enterprise_linux:5::client | kernel-PAE | before 0:2.6.18-53.1.19.el5 | 0:2.6.18-53.1.19.el5 |
| Red Hat:enterprise_linux:5::client | kernel-PAE-debuginfo | before 0:2.6.18-53.1.19.el5 | 0:2.6.18-53.1.19.el5 |
| Red Hat:enterprise_linux:5::client | kernel-PAE-devel | before 0:2.6.18-53.1.19.el5 | 0:2.6.18-53.1.19.el5 |
| Red Hat:enterprise_linux:5::client | kernel-xen | before 0:2.6.18-53.1.19.el5 | 0:2.6.18-53.1.19.el5 |
| Red Hat:enterprise_linux:5::client | kernel-xen-debuginfo | before 0:2.6.18-53.1.19.el5 | 0:2.6.18-53.1.19.el5 |
| Red Hat:enterprise_linux:5::client | kernel-xen-devel | before 0:2.6.18-53.1.19.el5 | 0:2.6.18-53.1.19.el5 |
| Red Hat:enterprise_linux:5::server | kernel-kdump | before 0:2.6.18-53.1.19.el5 | 0:2.6.18-53.1.19.el5 |
| Red Hat:enterprise_linux:5::server | kernel-kdump-debuginfo | before 0:2.6.18-53.1.19.el5 | 0:2.6.18-53.1.19.el5 |
| Red Hat:enterprise_linux:5::server | kernel-kdump-devel | before 0:2.6.18-53.1.19.el5 | 0:2.6.18-53.1.19.el5 |
Same product
xensource inc: all recordsOther highest-scoring records for the same primary product.
- CVE-2007-4993pygrub (tools/pygrub/src/GrubConf.py) in Xen 3.0.3, when booting a guest domain, allows local users with elevated privileges in the guest do27Monitor
- CVE-2007-5906Xen 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 b18Monitor
- CVE-2007-5907Xen 3.1.1 does not prevent modification of the CR4 TSC from applications, which allows pv guests to cause a denial of service (crash).18Monitor
- CVE-2007-6207Xen 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 8Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| red hat:kernel | 0:2.6.18-53.1.19.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-debug | 0:2.6.18-53.1.19.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:2.6.18-53.1.19.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:2.6.18-53.1.19.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:2.6.18-53.1.19.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-debuginfo-common | 0:2.6.18-53.1.19.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-devel | 0:2.6.18-53.1.19.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-doc | 0:2.6.18-53.1.19.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-headers | 0:2.6.18-53.1.19.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-PAE | 0:2.6.18-53.1.19.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-PAE-debuginfo | 0:2.6.18-53.1.19.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-PAE-devel | 0:2.6.18-53.1.19.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- P
Weakness class (CWE)
—
CVSS vector
AV:N/AC:M/Au:N/C:N/I:N/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.