First published: Fri Jan 22 2021(Updated: )
A NULL pointer dereference issue was found in the Floopy disk emulator of QEMU. It could occur while processing read/write ioport commands, if the selected Floopy drive is not initialised with a block device. A privileged guest user could use this flaw to crash the QEMU process on the host resulting in DoS scenario. Upstream patch: --------------- -> <a href="https://lists.nongnu.org/archive/html/qemu-devel/2021-01/msg05986.html">https://lists.nongnu.org/archive/html/qemu-devel/2021-01/msg05986.html</a>
Affected Software | Affected Version | How to fix |
---|---|---|
QEMU |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
REDHAT-BUG-1919210 is classified as a critical vulnerability due to its potential to crash the QEMU process.
To resolve REDHAT-BUG-1919210, ensure that the Floopy drive is properly initialized with a block device.
The vulnerability REDHAT-BUG-1919210 affects users of the QEMU emulator, specifically those utilizing the Floopy disk emulator without proper initialization.
REDHAT-BUG-1919210 is caused by a NULL pointer dereference when read/write IO port commands are processed for an uninitialized Floopy drive.
Yes, a privileged guest user can exploit REDHAT-BUG-1919210 to crash the QEMU process on the host system.