Hide Forgot
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: --------------- -> https://lists.gnu.org/archive/html/qemu-devel/2018-08/msg04892.html Reference: ---------- -> http://www.openwall.com/lists/oss-security/2018/08/28/6 -> https://lists.gnu.org/archive/html/qemu-devel/2018-08/msg02289.html
Acknowledgments: Name: Jann Horn (Google.com)
Created qemu tracking bugs for this issue: Affects: epel-7 [bug 1618358] Affects: fedora-all [bug 1618357]
This issue has been addressed in the following products: Red Hat OpenStack Platform 10.0 (Newton) Red Hat OpenStack Platform 13.0 (Queens) Red Hat OpenStack Platform 14.0 (Rocky) Via RHSA-2019:2425 https://access.redhat.com/errata/RHSA-2019:2425
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2018-15746
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2020:3906 https://access.redhat.com/errata/RHSA-2020:3906
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2020:3907 https://access.redhat.com/errata/RHSA-2020:3907