CVE-2020-13659 QEMU: exec: address_space_map returns NULL without setting length to zero may lead to DoS

                							

                <!--X-Body-Begin-->
<!--X-User-Header-->

oss-sec
mailing list archives
<!--X-User-Header-End-->
<!--X-TopPNI-->

By Date

By Thread

</form>

<!--X-TopPNI-End-->
<!--X-MsgBody-->
<!--X-Subject-Header-Begin-->
CVE-2020-13659 QEMU: exec: address_space_map returns NULL without setting length to zero may lead to DoS

<!--X-Subject-Header-End-->
<!--X-Head-of-Message-->

From: P J P &lt;ppandit () redhat com&gt;

Date: Mon, 1 Jun 2020 17:54:06 +0530 (IST)

<!--X-Head-of-Message-End-->
<!--X-Head-Body-Sep-Begin-->

<!--X-Head-Body-Sep-End-->
<!--X-Body-of-Message-->
  Hello,

A NULL pointer dereference issue was found in the MegaRAID SAS 8708EM2 
emulator of the QEMU. This issue occurs because the address_space_map() API 
while mapping physical memory into host's virtual address space may return 
NULL, without setting the length parameter to zero(0). A guest user/process 
may use this flaw to crash the QEMU process on the host resulting in DoS 
scenario.

Upstream patch:
---------------
  -&gt; https://lists.gnu.org/archive/html/qemu-devel/2020-05/msg07313.html

Reference:
----------
  -&gt; https://bugs.launchpad.net/qemu/+bug/1878259

Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
8685 545E B54C 486B C6EB 271E E285 8B5A F050 DE8D

<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->

<!--X-Follow-Ups-End-->
<!--X-References-->
<!--X-References-End-->
<!--X-BotPNI-->

By Date

By Thread

Current thread:

CVE-2020-13659 QEMU: exec: address_space_map returns NULL without setting length to zero may lead to DoS P J P (Jun 01)

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->