CVE-2018-1059

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.

These are all security issues fixed in the dpdk-19.11.8-2.7 package on the GA media of openSUSE Tumbleweed.

This update fixes the following issues:

• CVE-2018-1059: 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. (bsc#1089638).

This update for dpdk to version 16.11.8 provides the following security fix:

• CVE-2018-1059: restrict untrusted guest to misuse virtio to corrupt host application (ovs-dpdk) memory which could have lead all VM to lose connectivity (bsc#1089638)

and following non-security fixes:

• Enable the broadcom chipset family Broadcom NetXtreme II BCM57810 (bsc#1073363)
• Fix a latency problem by using cond_resched rather than schedule_timeout_interruptible (bsc#1069601)
• Fix a syntax error affecting csh environment configuration (bsc#1102310)
• Fixes in net/bnxt:
  • Fix HW Tx checksum offload check
  • Fix incorrect IO address handling in Tx
  • Fix Rx ring count limitation
  • Check access denied for HWRM commands
  • Fix RETA size
  • Fix close operation
• Fixes in eal/linux:
  • Fix an invalid syntax in interrupts
  • Fix return codes on thread naming failure
• Fixes in kni:
  • Fix crash with null name
  • Fix build with gcc 8.1
• Fixes in net/thunderx:
  • Fix build with gcc optimization on
  • Avoid sq door bell write on zero packet
• net/bonding: Fix MAC address reset
• vhost: Fix missing increment of log cache count

Maxime Coquelin discovered that DPDK incorrectly handled guest physical ranges. A malicious guest could use this issue to possibly access sensitive information.