CVE-2018-16847 json
An OOB heap buffer r/w access issue was found in the NVM Express Controller emulation in QEMU.
published 8y ago modified 4mo ago also EUVD-2018-8643
- cvss
- 7.0
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
An OOB heap buffer r/w access issue was found in the NVM Express Controller emulation in QEMU. It could occur in nvme_cmb_ops routines in nvme device. A guest user/process could use this flaw to crash the QEMU process resulting in DoS or potentially run arbitrary code with privileges of the QEMU process.
Patch / fix
- qemu Debian 14, Debian 13, Debian 12 1:3.1+dfsg-1
debian advisories DEBIAN-CVE-2018-16847
- qemu Ubuntu 18.04 LTS 1:2.11+dfsg-1ubuntu7.8
ubuntu advisories UBUNTU-CVE-2018-16847
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- qemu SLES for SAP 12 SP4, SLES 12 SP4, SLED 12 SP4 2.11.2-5.5.1
- qemu SLE Module for Server Applications 15, SLE Module for Basesystem 15 2.11.2-9.17.1
- qemu SLE Module for Server Applications 15, SLE Module for Basesystem 15 2.11.2-9.12.2
suse advisories SUSE-SU-2018:4185-1SUSE-SU-2018:4086-1SUSE-SU-2018:3927-1
Is CVE-2018-16847 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2018-16847 updated cvss 7.0
QEMU: nvme: Out-of-bounds r/w buffer access in cmb operations
-
Red Hat Enterprise Linux 5 kvm Red Hat Enterprise Linux 6 qemu-img, qemu-kvm, qemu-kvm-tools, qemu-guest-agent, qemu-guest-agent-win32 Red Hat Enterprise Linux 7 qemu-img, qemu-kvm, libcacard, qemu-img-ma, qemu-kvm-ma, qemu-kvm-rhev, +6 more Red Hat Enterprise Linux 8 qemu-img, qemu-kvm, qemu-kvm-core, qemu-kvm-tests, qemu-kvm-common, qemu-guest-agent, +8 more Red Hat OpenStack Platform 8 (Liberty) qemu-img-rhev, qemu-kvm-rhev, libcacard-rhev, qemu-kvm-tools-rhev, libcacard-devel-rhev, libcacard-tools-rhev, +1 more Red Hat OpenStack Platform 9 (Mitaka) qemu-img-rhev, qemu-kvm-rhev, libcacard-rhev, qemu-kvm-tools-rhev, libcacard-devel-rhev, libcacard-tools-rhev, +1 morenot affected: vulnerable code not present
+4 more productsfewer
Red Hat OpenStack Platform 10 (Newton) qemu-img-rhev, qemu-kvm-rhev, qemu-kvm-tools-rhev, qemu-kvm-common-rhev Red Hat OpenStack Platform 12 (Pike) qemu-img-rhev, qemu-kvm-rhev, qemu-kvm-tools-rhev, qemu-kvm-common-rhev Red Hat OpenStack Platform 13 (Queens) qemu-img-rhev, qemu-kvm-rhev, qemu-kvm-tools-rhev, qemu-kvm-common-rhev Red Hat OpenStack Platform 14 (Rocky) qemu-img-rhev, qemu-kvm-rhev, qemu-kvm-tools-rhev, qemu-kvm-common-rhev
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 7.0 | CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 4.6 | AV:L/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- [UNKNOWN] QEMU:
Classification
References
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2018-16847
issue-tracking, patch, third-party-advisory
-
openwall.com
/lists/oss-security/2018/11/02/1
mailing-list, patch, third-party-advisory
-
lists.gnu.org
/archive/html/qemu-devel/2018-11/msg00200.html
mailing-list, patch, third-party-advisory
-
usn.ubuntu.com
/3826-1/
vendor-advisory, third-party-advisory
-
securityfocus.com
/bid/105866
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-16847
- NVD CVE-2018-16847
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.