First published: Mon Aug 13 2018(Updated: )
An issue was found in the way QEMU implements Seccomp sandboxing. In that, all QEMU threads are not bound by the sandbox. A guest user/process maybe be able to use this flaw to invoke prohibited system calls on a host, resulting in guest crash. Upstream patch: --------------- -> <a href="https://lists.gnu.org/archive/html/qemu-devel/2018-08/msg04892.html">https://lists.gnu.org/archive/html/qemu-devel/2018-08/msg04892.html</a> Reference: ---------- -> <a href="http://www.openwall.com/lists/oss-security/2018/08/28/6">http://www.openwall.com/lists/oss-security/2018/08/28/6</a> -> <a href="https://lists.gnu.org/archive/html/qemu-devel/2018-08/msg02289.html">https://lists.gnu.org/archive/html/qemu-devel/2018-08/msg02289.html</a>
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/qemu-kvm | <10:1.5.3-175.el7 | 10:1.5.3-175.el7 |
redhat/qemu-kvm-ma | <10:2.12.0-48.el7 | 10:2.12.0-48.el7 |
redhat/qemu-kvm-rhev | <10:2.12.0-33.el7 | 10:2.12.0-33.el7 |
redhat/qemu-kvm-rhev | <10:2.12.0-48.el7 | 10:2.12.0-48.el7 |
QEMU qemu | <=3.0.1 | |
debian/qemu | 1:3.1+dfsg-8+deb10u8 1:3.1+dfsg-8+deb10u11 1:5.2+dfsg-11+deb11u3 1:5.2+dfsg-11+deb11u2 1:7.2+dfsg-7+deb12u3 1:8.1.2+ds-1 1:8.2.0+ds-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)