# CVE-2016-5403: Denial of service in n/a > Local guest administrators can crash the QEMU process and consume memory by submitting virtqueue requests without waiting for completion. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 2 Aug 2016 - **Updated:** 6 Aug 2024 - **Also known as:** ALPINE-CVE-2016-5403, DEBIAN-CVE-2016-5403, GHSA-w9gj-prpq-pxm9, RHSA-2016:1585, RHSA-2016:1586, RHSA-2016:1652, UBUNTU-CVE-2016-5403, USN-3047-2 ## What is CVE-2016-5403? CVE-2016-5403 is a medium-severity denial of service vulnerability in Canonical Ubuntu Linux, published on 2 Aug 2016. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description The virtqueue_pop function in hw/virtio/virtio.c in QEMU allows local guest OS administrators to cause a denial of service (memory consumption and QEMU process crash) by submitting requests without waiting for completion. Weakness: CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2016-5403? It affects 13 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `qemu-guest-agent` | Red Hat:enterprise_linux:6::client | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-img` | Red Hat:enterprise_linux:6::client | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-kvm` | Red Hat:enterprise_linux:6::client | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-kvm-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-kvm-tools` | Red Hat:enterprise_linux:6::client | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-guest-agent` | Red Hat:enterprise_linux:6::computenode | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-img` | Red Hat:enterprise_linux:6::computenode | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-kvm` | Red Hat:enterprise_linux:6::computenode | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-kvm-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-kvm-tools` | Red Hat:enterprise_linux:6::computenode | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-img-rhev` | Red Hat:enterprise_linux:6::hypervisor | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-kvm-rhev` | Red Hat:enterprise_linux:6::hypervisor | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-kvm-rhev-debuginfo` | Red Hat:enterprise_linux:6::hypervisor | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-kvm-rhev-tools` | Red Hat:enterprise_linux:6::hypervisor | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-guest-agent` | Red Hat:enterprise_linux:6::server | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-img` | Red Hat:enterprise_linux:6::server | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-kvm` | Red Hat:enterprise_linux:6::server | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-kvm-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-kvm-tools` | Red Hat:enterprise_linux:6::server | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-guest-agent` | Red Hat:enterprise_linux:6::workstation | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-img` | Red Hat:enterprise_linux:6::workstation | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-kvm` | Red Hat:enterprise_linux:6::workstation | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-kvm-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-kvm-tools` | Red Hat:enterprise_linux:6::workstation | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-img-rhev` | Red Hat:openstack:5::el6 | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-kvm-rhev` | Red Hat:openstack:5::el6 | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-kvm-rhev-debuginfo` | Red Hat:openstack:5::el6 | All versions | 2:0.12.1.2-2.491.el6_8.3 | | `qemu-kvm-rhev-tools` | Red Hat:openstack:5::el6 | All versions | 2:0.12.1.2-2.491.el6_8.3 | Products: Canonical Ubuntu Linux, Debian Debian Linux, Oracle Linux, Oracle Vm Server, Qemu Qemu, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Eus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation, Redhat Openstack, Redhat Virtualization. ## How do I fix CVE-2016-5403? Apply the vendor's patch. ## Is CVE-2016-5403 being exploited? There is no known exploitation of CVE-2016-5403 in the wild and no public exploit code. ## Other vulnerabilities in Canonical Ubuntu Linux - [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild) - [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2016-5403 and fix it if it is affected. What it is: CVE-2016-5403 is a medium-severity denial of service vulnerability in Canonical Ubuntu Linux, published on 2 Aug 2016. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2016-5403 in the wild and no public exploit code. Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2016-5403/ (Markdown: https://insights.sbomify.com/CVE-2016-5403/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2016-5403 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-5403 - OSV: https://osv.dev/vulnerability/CVE-2016-5403 --- From sbomify Insights: https://insights.sbomify.com/CVE-2016-5403/ Summaries are generated and may contain mistakes; the official description above is the record.