CVE-2018-20126
hw/rdma/vmw/pvrdma_cmd.c in QEMU allows create_cq and create_qp memory leaks because errors are...
hw/rdma/vmw/pvrdma_cmd.c in QEMU allows create_cq and create_qp memory leaks because errors are mishandled.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
5.5
hw/rdma/vmw/pvrdma_cmd.c in QEMU allows create_cq and create_qp memory leaks because errors are mishandled.
- Record
CVE-2018-20126- CVSS 3.1
- 5.5 Medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - CVSS 2.0
- 2.1 Low
AV:L/AC:L/Au:N/C:N/I:N/A:P - Weakness
- CWE-772
- Updated
- 2026-11-02
CVE List No score
hw/rdma/vmw/pvrdma_cmd.c in QEMU allows create_cq and create_qp memory leaks because errors are mishandled.
- Record
CVE-2018-20126- Updated
- 2026-11-02
EUVDEUVD-2018-12696 No score
hw/rdma/vmw/pvrdma_cmd.c in QEMU allows create_cq and create_qp memory leaks because errors are mishandled.
- Record
EUVD-2018-12696- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-23f5-q32q-xcxm
5.5
hw/rdma/vmw/pvrdma_cmd.c in QEMU allows create_cq and create_qp memory leaks because errors are...
hw/rdma/vmw/pvrdma_cmd.c in QEMU allows create_cq and create_qp memory leaks because errors are mishandled.
- Record
GHSA-23f5-q32q-xcxm- CVSS 3.1
- 5.5 Medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-772
- Updated
- 2026-11-02
OSV
5.5
hw/rdma/vmw/pvrdma_cmd.c in QEMU allows create_cq and create_qp memory leaks because errors are mishandled.
- Record
CVE-2018-20126- CVSS 3.1
- 5.5 Medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVDEBIAN-CVE-2018-20126
5.5
hw/rdma/vmw/pvrdma_cmd.c in QEMU allows create_cq and create_qp memory leaks because errors are mishandled.
- Record
DEBIAN-CVE-2018-20126- CVSS 3.1
- 5.5 Medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
Show 6 moreShow less
OSVopenSUSE-SU-2019:2505-1 No score
Security update for qemu
This update for qemu fixes the following issues:
- Patch queue updated from https://gitlab.suse.de/virtualization/qemu.git SLE15
- Fix use-after-free in slirp (CVE-2018-20126 bsc#1119991)
- Fix potential DOS in lsi scsi controller emulation (CVE-2019-12068 bsc#1146873)
- Expose taa-no 'feature', indicating CPU does not have the TSX Async Abort vulnerability. (CVE-2019-11135 bsc#1152506)
- Expose pschange-mc-no 'feature', indicating CPU does not have the page size change machine check vulnerability (CVE-2018-12207 bsc#1155812)
This update was imported from the SUSE:SLE-15:Update update project.
- Record
openSUSE-SU-2019:2505-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2019:2510-1 No score
Security update for qemu
This update for qemu fixes the following issues:
qemu was updated to v3.1.1.1, a stable, bug-fix-only release, which includes 2 fixes we already carry, as well as one additional use- after-free fix in slirp. (CVE-2018-20126 bsc#1119991, CVE-2019-14378 bsc#1143794, and CVE-2019-15890 bsc#1149811 respectively)
Security issues fixed:
- CVE-2019-12068: Fixed potential DOS in lsi scsi controller emulation (bsc#1146873)
- CVE-2019-11135: Expose taa-no 'feature', indicating CPU does not have the TSX Async Abort vulnerability. (bsc#1152506)
- CVE-2018-12207: Expose pschange-mc-no 'feature', indicating CPU does not have the page size change machine check vulnerability (bsc#1117665)
Other issues fixed:
- Change how this bug gets fixed (bsc#1144087)
- Disable file locking in the Xen PV disk backend to avoid locking issues with PV domUs during migration. The issues triggered by the locking can not be properly handled in libxl. The locking introduced in qemu-2.10 was removed again in qemu-4.0. (bsc#1079730, bsc#1098403, bsc#1111025, bsc#1145427, bsc#1145774)
- Feature support for vfio-ccw dasd ipl (bsc#1145379 jira-SLE-6132)
- Additional hardware instruction support for s390, also update qemu linux headers to 5.2-rc1 (bsc#1145436 jira-SLE-6237)
This update was imported from the SUSE:SLE-15-SP1:Update update project.
- Record
openSUSE-SU-2019:2510-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:11287-1 No score
qemu-6.1.0-32.1 on GA media
These are all security issues fixed in the qemu-6.1.0-32.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:11287-1- Updated
- 2026-11-02
OSVSUSE-SU-2019:2954-1 No score
Security update for qemu
This update for qemu fixes the following issues:
- Patch queue updated from https://gitlab.suse.de/virtualization/qemu.git SLE15
- Fix use-after-free in slirp (CVE-2018-20126 bsc#1119991)
- Fix potential DOS in lsi scsi controller emulation (CVE-2019-12068 bsc#1146873)
- Expose taa-no 'feature', indicating CPU does not have the TSX Async Abort vulnerability. (CVE-2019-11135 bsc#1152506)
- Expose pschange-mc-no 'feature', indicating CPU does not have the page size change machine check vulnerability (CVE-2018-12207 bsc#1155812)
- Record
SUSE-SU-2019:2954-1- Updated
- 2026-11-02
OSVSUSE-SU-2019:2955-1 No score
Security update for qemu
This update for qemu fixes the following issues:
qemu was updated to v3.1.1.1, a stable, bug-fix-only release, which includes 2 fixes we already carry, as well as one additional use- after-free fix in slirp. (CVE-2018-20126 bsc#1119991, CVE-2019-14378 bsc#1143794, and CVE-2019-15890 bsc#1149811 respectively)
Security issues fixed:
- CVE-2019-12068: Fixed potential DOS in lsi scsi controller emulation (bsc#1146873)
- CVE-2019-11135: Expose taa-no 'feature', indicating CPU does not have the TSX Async Abort vulnerability. (bsc#1152506)
- CVE-2018-12207: Expose pschange-mc-no 'feature', indicating CPU does not have the page size change machine check vulnerability (bsc#1117665)
Other issues fixed:
- Change how this bug gets fixed (bsc#1144087)
- Disable file locking in the Xen PV disk backend to avoid locking issues with PV domUs during migration. The issues triggered by the locking can not be properly handled in libxl. The locking introduced in qemu-2.10 was removed again in qemu-4.0. (bsc#1079730, bsc#1098403, bsc#1111025, bsc#1145427, bsc#1145774)
- Feature support for vfio-ccw dasd ipl (bsc#1145379 jira-SLE-6132)
- Additional hardware instruction support for s390, also update qemu linux headers to 5.2-rc1 (bsc#1145436 jira-SLE-6237)
- Record
SUSE-SU-2019:2955-1- Updated
- 2026-11-02
OSVSUSE-SU-2019:2956-1 No score
Security update for qemu
This update for qemu fixes the following issues:
-
Remove a backslash '' escape character from 80-qemu-ga.rules (bsc#1153358) Unlike sles 15 or newer guests, The udev rule file of qemu guest agent in sles 12 sp4 or newer guest only needs one escape character.
-
Fix use-after-free in slirp (CVE-2018-20126 bsc#1119991)
-
Fix potential DOS in lsi scsi controller emulation (CVE-2019-12068 bsc#1146873)
-
Expose taa-no 'feature', indicating CPU does not have the TSX Async Abort vulnerability. (CVE-2019-11135 bsc#1152506)
-
Expose pschange-mc-no 'feature', indicating CPU does not have the page size change machine check vulnerability (CVE-2018-12207 bsc#1155812)
-
Patch queue updated from https://gitlab.suse.de/virtualization/qemu.git SLE12-SP4
- Record
SUSE-SU-2019:2956-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
qemuDebian:12 |
before 1:4.1-1 | 1:4.1-1 |
qemuDebian:13 |
before 1:4.1-1 | 1:4.1-1 |
qemuDebian:14 |
before 1:4.1-1 | 1:4.1-1 |
qemuSUSE:Linux Enterprise Module for Basesystem 15 From an advisory covering 4 CVEs |
before 2.11.2-9.33.1 | 2.11.2-9.33.1 |
qemuSUSE:Linux Enterprise Module for Server Applications 15 From an advisory covering 4 CVEs |
before 2.11.2-9.33.1 | 2.11.2-9.33.1 |
qemuSUSE:Linux Enterprise Module for Basesystem 15 SP1 From an advisory covering 6 CVEs |
before 3.1.1.1-9.6.2 | 3.1.1.1-9.6.2 |
qemuSUSE:Linux Enterprise Module for Server Applications 15 SP1 From an advisory covering 6 CVEs |
before 3.1.1.1-9.6.2 | 3.1.1.1-9.6.2 |
qemuSUSE:Linux Enterprise Desktop 12 SP4 From an advisory covering 4 CVEs |
before 2.11.2-5.23.2 | 2.11.2-5.23.2 |
qemuSUSE:Linux Enterprise Server 12 SP4 From an advisory covering 4 CVEs |
before 2.11.2-5.23.2 | 2.11.2-5.23.2 |
qemuSUSE:Linux Enterprise Server for SAP Applications 12 SP4 From an advisory covering 4 CVEs |
before 2.11.2-5.23.2 | 2.11.2-5.23.2 |
Show 4 moreShow less
| Package | Affected | Fixed |
|---|---|---|
qemuopenSUSE:Leap 15.0 From an advisory covering 4 CVEs |
before 2.11.2-lp150.7.28.1 | 2.11.2-lp150.7.28.1 |
qemuopenSUSE:Leap 15.1 From an advisory covering 6 CVEs |
before 3.1.1.1-lp151.7.6.1 | 3.1.1.1-lp151.7.6.1 |
qemu-linux-useropenSUSE:Leap 15.1 From an advisory covering 6 CVEs |
before 3.1.1.1-lp151.7.6.1 | 3.1.1.1-lp151.7.6.1 |
qemuopenSUSE:Tumbleweed From an advisory covering 135 CVEs |
before 6.1.0-32.1 | 6.1.0-32.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2018-20126 is a medium vulnerability (CVSS 5.5) in Qemu, published December 20, 2018. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.49%, the 42nd percentile. Fixed in qemu 1:4.1-1.
References
openwall.com/lists/oss-security/2018/12/19/4
lists.gnu.org/archive/html/qemu-devel/2018-12/msg02824.html
securityfocus.com/bid/106298
usn.ubuntu.com/3923-1
lists.opensuse.org/opensuse-security-announce/2019-11/msg00034.html
lists.opensuse.org/opensuse-security-announce/2019-11/msg00038.html
Show 162 moreShow less
nvd.nist.gov/vuln/detail/CVE-2018-20126
github.com/advisories/GHSA-23f5-q32q-xcxm
security-tracker.debian.org/tracker/CVE-2018-20126
suse.com/support/update/announcement/2019/suse-su-20192954-1
bugzilla.suse.com/1119991
bugzilla.suse.com/1146873
bugzilla.suse.com/1152506
bugzilla.suse.com/1155812
suse.com/security/cve/CVE-2018-12207
suse.com/security/cve/CVE-2018-20126
suse.com/security/cve/CVE-2019-11135
suse.com/security/cve/CVE-2019-12068
suse.com/support/update/announcement/2019/suse-su-20192955-1
bugzilla.suse.com/1079730
bugzilla.suse.com/1098403
bugzilla.suse.com/1111025
bugzilla.suse.com/1117665
bugzilla.suse.com/1143794
bugzilla.suse.com/1144087
bugzilla.suse.com/1145379
bugzilla.suse.com/1145427
bugzilla.suse.com/1145436
bugzilla.suse.com/1145774
bugzilla.suse.com/1149811
suse.com/security/cve/CVE-2019-14378
suse.com/security/cve/CVE-2019-15890
bugzilla.suse.com/SLE-6132
bugzilla.suse.com/SLE-6237
suse.com/support/update/announcement/2019/suse-su-20192956-1
bugzilla.suse.com/1153358
lists.opensuse.org/archives/list/[email protected]/thread/YGK33QVVCMOM3HRWRJ6FPIFV2JBB4XDB
lists.opensuse.org/archives/list/[email protected]/thread/KGVFZGJMBR53343ITOTWO7YW2JVKGHDT
suse.com/security/cve/CVE-2014-0222
suse.com/security/cve/CVE-2014-8106
suse.com/security/cve/CVE-2015-5225
suse.com/security/cve/CVE-2015-6855
suse.com/security/cve/CVE-2015-8504
suse.com/security/cve/CVE-2015-8619
suse.com/security/cve/CVE-2016-10028
suse.com/security/cve/CVE-2016-10155
suse.com/security/cve/CVE-2016-1714
suse.com/security/cve/CVE-2016-6490
suse.com/security/cve/CVE-2016-6836
suse.com/security/cve/CVE-2016-7156
suse.com/security/cve/CVE-2016-7157
suse.com/security/cve/CVE-2016-7161
suse.com/security/cve/CVE-2016-7170
suse.com/security/cve/CVE-2016-7421
suse.com/security/cve/CVE-2016-7422
suse.com/security/cve/CVE-2016-7423
suse.com/security/cve/CVE-2016-7466
suse.com/security/cve/CVE-2016-7907
suse.com/security/cve/CVE-2016-7908
suse.com/security/cve/CVE-2016-7909
suse.com/security/cve/CVE-2016-7994
suse.com/security/cve/CVE-2016-7995
suse.com/security/cve/CVE-2016-8576
suse.com/security/cve/CVE-2016-8577
suse.com/security/cve/CVE-2016-8578
suse.com/security/cve/CVE-2016-8667
suse.com/security/cve/CVE-2016-8668
suse.com/security/cve/CVE-2016-8669
suse.com/security/cve/CVE-2016-8909
suse.com/security/cve/CVE-2016-8910
suse.com/security/cve/CVE-2016-9101
suse.com/security/cve/CVE-2016-9102
suse.com/security/cve/CVE-2016-9103
suse.com/security/cve/CVE-2016-9104
suse.com/security/cve/CVE-2016-9105
suse.com/security/cve/CVE-2016-9106
suse.com/security/cve/CVE-2016-9602
suse.com/security/cve/CVE-2016-9907
suse.com/security/cve/CVE-2016-9921
suse.com/security/cve/CVE-2017-10664
suse.com/security/cve/CVE-2017-10806
suse.com/security/cve/CVE-2017-11334
suse.com/security/cve/CVE-2017-11434
suse.com/security/cve/CVE-2017-13673
suse.com/security/cve/CVE-2017-13711
suse.com/security/cve/CVE-2017-14167
suse.com/security/cve/CVE-2017-15038
suse.com/security/cve/CVE-2017-15118
suse.com/security/cve/CVE-2017-15268
suse.com/security/cve/CVE-2017-15289
suse.com/security/cve/CVE-2017-2615
suse.com/security/cve/CVE-2017-2620
suse.com/security/cve/CVE-2017-2630
suse.com/security/cve/CVE-2017-5525
suse.com/security/cve/CVE-2017-5526
suse.com/security/cve/CVE-2017-5552
suse.com/security/cve/CVE-2017-5578
suse.com/security/cve/CVE-2017-5579
suse.com/security/cve/CVE-2017-5667
suse.com/security/cve/CVE-2017-5715
suse.com/security/cve/CVE-2017-5856
suse.com/security/cve/CVE-2017-5857
suse.com/security/cve/CVE-2017-5898
suse.com/security/cve/CVE-2017-5973
suse.com/security/cve/CVE-2017-6058
suse.com/security/cve/CVE-2017-7471
suse.com/security/cve/CVE-2017-7493
suse.com/security/cve/CVE-2017-8112
suse.com/security/cve/CVE-2017-8309
suse.com/security/cve/CVE-2017-8379
suse.com/security/cve/CVE-2017-8380
suse.com/security/cve/CVE-2017-9503
suse.com/security/cve/CVE-2017-9524
suse.com/security/cve/CVE-2018-10839
suse.com/security/cve/CVE-2018-11806
suse.com/security/cve/CVE-2018-12126
suse.com/security/cve/CVE-2018-12130
suse.com/security/cve/CVE-2018-15746
suse.com/security/cve/CVE-2018-16872
suse.com/security/cve/CVE-2018-17963
suse.com/security/cve/CVE-2018-20123
suse.com/security/cve/CVE-2018-20124
suse.com/security/cve/CVE-2018-20125
suse.com/security/cve/CVE-2018-20191
suse.com/security/cve/CVE-2018-20216
suse.com/security/cve/CVE-2018-20815
suse.com/security/cve/CVE-2018-3639
suse.com/security/cve/CVE-2018-7858
suse.com/security/cve/CVE-2019-03812
suse.com/security/cve/CVE-2019-12155
suse.com/security/cve/CVE-2019-13164
suse.com/security/cve/CVE-2019-6778
suse.com/security/cve/CVE-2019-8934
suse.com/security/cve/CVE-2019-9824
suse.com/security/cve/CVE-2020-10702
suse.com/security/cve/CVE-2020-10717
suse.com/security/cve/CVE-2020-10761
suse.com/security/cve/CVE-2020-11102
suse.com/security/cve/CVE-2020-11869
suse.com/security/cve/CVE-2020-13361
suse.com/security/cve/CVE-2020-13362
suse.com/security/cve/CVE-2020-13659
suse.com/security/cve/CVE-2020-13800
suse.com/security/cve/CVE-2020-14364
suse.com/security/cve/CVE-2020-16092
suse.com/security/cve/CVE-2020-1711
suse.com/security/cve/CVE-2020-17380
suse.com/security/cve/CVE-2020-1983
suse.com/security/cve/CVE-2020-25085
suse.com/security/cve/CVE-2020-25723
suse.com/security/cve/CVE-2020-27821
suse.com/security/cve/CVE-2020-29129
suse.com/security/cve/CVE-2020-7039
suse.com/security/cve/CVE-2020-8608
suse.com/security/cve/CVE-2021-20181
suse.com/security/cve/CVE-2021-20203
suse.com/security/cve/CVE-2021-20221
suse.com/security/cve/CVE-2021-20257
suse.com/security/cve/CVE-2021-20263
suse.com/security/cve/CVE-2021-3416
suse.com/security/cve/CVE-2021-3527
suse.com/security/cve/CVE-2021-3544
suse.com/security/cve/CVE-2021-3545
suse.com/security/cve/CVE-2021-3546
suse.com/security/cve/CVE-2021-3582
suse.com/security/cve/CVE-2021-3607
suse.com/security/cve/CVE-2021-3608
suse.com/security/cve/CVE-2021-3682