Bug 1906432 - QEMU: divide by zero in exynos4210_ltick_cnt_get_cnto() in hw/timer/exynos4210_mct.c
Summary: QEMU: divide by zero in exynos4210_ltick_cnt_get_cnto() in hw/timer/exynos421...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1906528 1906529
Blocks: 1902762
TreeView+ depends on / blocked
 
Reported: 2020-12-10 13:59 UTC by Mauro Matteo Cascella
Modified: 2021-02-16 18:45 UTC (History)
34 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-12-10 18:47:02 UTC
Embargoed:


Attachments (Terms of Use)

Description Mauro Matteo Cascella 2020-12-10 13:59:13 UTC
A divide by zero issue was found in the Samsung exynos4210 multi core timer emulation of QEMU, available through arm/aarch64 targets. Specifically, function exynos4210_ltick_cnt_get_cnto() in hw/timer/exynos4210_mct.c does not properly validate the local timer's TCNTB field while using its value in a modulo operation 'remain % s->tcntb'. A guest user may be able to exploit this issue to crash the QEMU process on the host, resulting in a denial of service.

Comment 1 Mauro Matteo Cascella 2020-12-10 13:59:20 UTC
Acknowledgments:

Name: Gaoning Pan (Zhejiang University)

Comment 2 Mauro Matteo Cascella 2020-12-10 17:50:04 UTC
Created qemu tracking bugs for this issue:

Affects: epel-7 [bug 1906529]
Affects: fedora-all [bug 1906528]

Comment 4 Mauro Matteo Cascella 2020-12-11 14:08:01 UTC
Statement:

This issue does not affect the versions of `qemu-kvm` as shipped with Red Hat products, as they do not include support for the Exynos4210 platform emulation. Additionally, Red Hat Product Security does not consider this bug to be a security vulnerability because it only affects the non-virtualization use case. For further information, please refer to the QEMU Security page: https://www.qemu.org/docs/master/system/security.html.


Note You need to log in before you can comment on or make changes to this bug.