CVE-2016-1922
What it is
QEMU (aka Quick Emulator) built with the TPR optimization for 32-bit Windows guests support is vulnerable to a null pointer dereference flaw. It occurs while doing I/O port write operations via hmp interface. In that, 'current_cpu' remains null, which leads to the null pointer dereference. A user or process could use this flaw to crash the QEMU instance, resulting in DoS issue.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.4% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.4% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.4% · EPSS, next 30 days
- Weakness
- CWE-476 · NULL pointer dereference
- Record status
- Modified
Affected
- Qemu ≤ 2.5.1.1
- Debian Linux 7.0
- Debian Linux 8.0
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2016-1922.md and follow it. Check whether this project is affected by CVE-2016-1922. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg02812.html
- https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg02812.html
References
- http://www.debian.org/security/2016/dsa-3469
- http://www.debian.org/security/2016/dsa-3470
- http://www.debian.org/security/2016/dsa-3471
- http://www.openwall.com/lists/oss-security/2016/01/16/1
- http://www.openwall.com/lists/oss-security/2016/01/16/6
- http://www.securityfocus.com/bid/81058
- https://bugzilla.redhat.com/show_bug.cgi?id=1283934
- https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg02812.html
- https://security.gentoo.org/glsa/201604-01
- http://www.debian.org/security/2016/dsa-3469
- http://www.debian.org/security/2016/dsa-3470
- http://www.debian.org/security/2016/dsa-3471
- http://www.openwall.com/lists/oss-security/2016/01/16/1
- http://www.openwall.com/lists/oss-security/2016/01/16/6
- http://www.securityfocus.com/bid/81058
- https://bugzilla.redhat.com/show_bug.cgi?id=1283934
- https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg02812.html
- https://security.gentoo.org/glsa/201604-01