From: Alexander Bulekov <1892761@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1892761] Re: Heap-use-after-free through double-fetch in ehci
Date: Mon, 14 Jun 2021 23:51:38 -0000 [thread overview]
Message-ID: <162371469824.17812.11971599419890054889.malone@gac.canonical.com> (raw)
In-Reply-To: 159828509705.1974.10240334178612192608.malonedeb@chaenomeles.canonical.com
No. If we figure out some way to consistently reproduce double-fetches
in a non-fuzzer build, I'll report the issue again, but this can
probably be closed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892761
Title:
Heap-use-after-free through double-fetch in ehci
Status in QEMU:
Incomplete
Bug description:
Hello,
I don't have a qtest reproducer for this crash because it involves a DMA double-fetch, and I don't think we can reproduce those with qtest.
Instead, I attached the pseudo-qtest trace produced by the fuzzer, along with some trace events.
The lines annotated with [DMA] are write commands that were triggered by a callback from a DMA read by the device. The lines annotated with [DOUBLE-FETCH] are DMA accesses that hit the same address more than once (possible double-fetches).
I am still thinking of nicer ways of presenting this trace and providing a reproducer.
-Alex
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1892761/+subscriptions
next prev parent reply other threads:[~2021-06-15 0:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 16:04 [Bug 1892761] [NEW] Heap-use-after-free through double-fetch in ehci Alexander Bulekov
2021-05-27 15:11 ` [Bug 1892761] " Thomas Huth
2021-06-14 23:51 ` Alexander Bulekov [this message]
2021-07-16 17:22 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=162371469824.17812.11971599419890054889.malone@gac.canonical.com \
--to=1892761@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.