dbcve.org
Debian LinuxOperating system · Debian

CVE-2019-17345

MEDIUM · 6.5 CVSS v3.1 Published 2019-10-08
Fix available
A fix is available. Upgrade to after 4.11.2 or later.
See remediation →
67/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue was discovered in Xen 4.8.x through 4.11.x allowing x86 PV guest OS users to cause a denial of service because mishandling of failed IOMMU operations causes a bug check during the cleanup of a crashed guest.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Xen 4.8.x through 4.11.x, x86 PV (paravirtualized) guest users can trigger a denial of service by causing failed IOMMU operations during crash cleanup of their guest domain. The hypervisor mishandles these failures, resulting in a bug check that crashes the host.

MitigationApply Xen security patches to properly handle failed IOMMU operations during guest crash cleanup, or upgrade to a patched Xen version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 9.0= 10.0
XenOperating system
Affected:>= 4.8.0, <= 4.11.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Xen hypervisor is installed
    Run 'xl list' or 'xm list' to list running domains, or check for Xen packages with 'dpkg -l | grep xen' on Debian
    Affected if Xen hypervisor is present on the system
  2. Check Xen version
    Run 'xl version' or 'xm version' to get the installed Xen version number
    Affected if Version is >= 4.8.0 and <= 4.11.2
  3. Identify running PV guest domains
    Run 'xl list' and look for domains with 'pv' in the type column, or check domain config files in /etc/xen/ for 'builder = "pv"'
    Affected if x86 paravirtualized (PV) guest domains are configured or running
  4. Confirm IOMMU/VT-d is enabled
    Check hypervisor boot parameters in /boot/grub/grub.cfg for 'iommu=1' or 'intel_iommu=on', or run 'xl dmesg | grep -i iommu'
    Affected if IOMMU support is enabled in the hypervisor

The system is affected if running Xen version 4.8.0 through 4.11.2 with x86 PV guests and IOMMU enabled, where a malicious guest can trigger failed IOMMU operations during crash cleanup to crash the host.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 4.11.2
Interim mitigation

Apply Xen security patches to properly handle failed IOMMU operations during guest crash cleanup, or upgrade to a patched Xen version.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,576.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-17345 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-17345 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data