dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2018-1059

MEDIUM · 6.1 CVSS v3.0 Published 2018-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
No privileges 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
The DPDK vhost-user interface does not check to verify that all the requested guest physical range is mapped and contiguous when performing Guest Physical Addresses to Host Virtual Addresses translations. This may lead to a malicious guest exposing vhost-user backend process memory. All versions before 18.02.1 are vulnerable.

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

The DPDK vhost-user interface fails to validate that requested guest physical address ranges are properly mapped and contiguous during GPA-to-HVA translation. This missing validation allows a malicious guest VM to read potentially sensitive memory from the vhost-user backend process, causing an information disclosure from guest to host context.

MitigationUpgrade DPDK to version 18.02.1 or later which contains the fix. Additionally, ensure proper memory mapping validation is enforced in the vhost-user backend configuration.

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
Ubuntu LinuxOperating system
Affected:= 17.10= 18.04
Ceph StorageApplication
Affected:= 3.0
Enterprise Linux Fast DatapathApplication
Affected:= 7.0
OpenshiftApplication
Affected:= 3.0
OpenstackApplication
Affected:= 8= 9= 10= 11= 12
VirtualizationApplication
Affected:= 4.0= 4.1
Virtualization ManagerApplication
Affected:= 4.1
Enterprise LinuxOperating system
Affected:= 7.0

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
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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

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. Identify DPDK installation and version
    Run 'dpkg -l | grep dpdk' or 'rpm -qa | grep dpdk' to list installed DPDK packages, then check the installed version against the vulnerable versions (17.10, 18.04 for Ubuntu; DPDK in RHEL 7.0, RHOSP 8-12, RHV 4.0-4.1, RHCS 3.0, RH OCP 3.0, RH Fast Datapath 7.0)
    Affected if DPDK is installed and the version matches or falls within the affected product/version ranges listed in the CVE
  2. Check for active vhost-user interfaces
    Run 'ls -la /var/run/openvswitch/vhost-user-*' or check for vhost-user socket files in /var/run/ (commonly /var/run/qemu/vhost-user-* or /var/run/virtio-forwarder/)
    Affected if vhost-user socket interfaces exist and are actively used by the system, indicating DPDK vhost-user backends are configured
  3. Verify vhost-user backend configuration
    Review the QEMU/libvirt configuration files or container orchestration manifests that define vhost-user interfaces. Look for 'vhost-user' type network devices in domain XML files (virsh dumpxml) or container pod specs
    Affected if The environment uses vhost-user interfaces to connect guest VMs to DPDK-based backends (such as Open vSwitch with DPDK)

A system is affected if it runs DPDK with vhost-user interfaces enabled and the installed DPDK or product version matches the vulnerable releases listed in the CVE advisory.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade DPDK to version 18.02.1 or later which contains the fix. Additionally, ensure proper memory mapping validation is enforced in the vhost-user backend configuration.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1059 — 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-2018-1059 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