Closed l2dy closed 6 years ago
http://www.openwall.com/lists/oss-security/2018/08/28/6
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 crash a guest resulting in DoS.
-> https://lists.gnu.org/archive/html/qemu-devel/2018-08/msg04892.html
-> https://lists.gnu.org/archive/html/qemu-devel/2018-08/msg02289.html
amd64
arm64
armel
ppc64
powerpc
Fixed with https://github.com/AOSC-Dev/aosc-os-abbs/commit/87486a0ca9ffff998267b4b8ccb16e2d5983649f. Closing.
Use AOSA-2018-0389.
http://www.openwall.com/lists/oss-security/2018/08/28/6
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 crash a guest resulting in DoS.
Upstream patch:
-> https://lists.gnu.org/archive/html/qemu-devel/2018-08/msg04892.html
Reference:
-> https://lists.gnu.org/archive/html/qemu-devel/2018-08/msg02289.html
Architectural progress
amd64
)arm64
)armel
)ppc64
)powerpc
)