qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org,
	"Philippe Mathieu-Daudé" <philippe.mathieu.daude@gmail.com>,
	"Bin Meng" <bin.meng@windriver.com>
Cc: "Laurent Vivier" <lvivier@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	qemu-block@nongnu.org, "David Hildenbrand" <david@redhat.com>,
	"Jason Wang" <jasowang@redhat.com>, "Li Qiang" <liq3ea@gmail.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Peter Xu" <peterx@redhat.com>,
	"Qiuhao Li" <Qiuhao.Li@outlook.com>,
	"Darren Kenny" <darren.kenny@oracle.com>,
	"Bandan Das" <bsd@redhat.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Edgar E . Iglesias" <edgar.iglesias@gmail.com>,
	"Alexander Bulekov" <alxndr@bu.edu>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [RFC PATCH 2/3] hw/sd/sdhci: Prohibit DMA accesses to devices
Date: Fri, 18 Mar 2022 19:38:45 +0100	[thread overview]
Message-ID: <cdf34ed8-a6bc-946f-a254-4b736fff3ff1@redhat.com> (raw)
In-Reply-To: <20211215205656.488940-3-philmd@redhat.com>

On 15/12/2021 21.56, Philippe Mathieu-Daudé wrote:
> From: Philippe Mathieu-Daudé <f4bug@amsat.org>
> 
> The issue reported by OSS-Fuzz produces the following backtrace:
> 
>    ==447470==ERROR: AddressSanitizer: heap-buffer-overflow
>    READ of size 1 at 0x61500002a080 thread T0
>        #0 0x71766d47 in sdhci_read_dataport hw/sd/sdhci.c:474:18
>        #1 0x7175f139 in sdhci_read hw/sd/sdhci.c:1022:19
>        #2 0x721b937b in memory_region_read_accessor softmmu/memory.c:440:11
>        #3 0x72171e51 in access_with_adjusted_size softmmu/memory.c:554:18
>        #4 0x7216f47c in memory_region_dispatch_read1 softmmu/memory.c:1424:16
>        #5 0x7216ebb9 in memory_region_dispatch_read softmmu/memory.c:1452:9
>        #6 0x7212db5d in flatview_read_continue softmmu/physmem.c:2879:23
>        #7 0x7212f958 in flatview_read softmmu/physmem.c:2921:12
>        #8 0x7212f418 in address_space_read_full softmmu/physmem.c:2934:18
>        #9 0x721305a9 in address_space_rw softmmu/physmem.c:2962:16
>        #10 0x7175a392 in dma_memory_rw_relaxed include/sysemu/dma.h:89:12
>        #11 0x7175a0ea in dma_memory_rw include/sysemu/dma.h:132:12
>        #12 0x71759684 in dma_memory_read include/sysemu/dma.h:152:12
>        #13 0x7175518c in sdhci_do_adma hw/sd/sdhci.c:823:27
>        #14 0x7174bf69 in sdhci_data_transfer hw/sd/sdhci.c:935:13
>        #15 0x7176aaa7 in sdhci_send_command hw/sd/sdhci.c:376:9
>        #16 0x717629ee in sdhci_write hw/sd/sdhci.c:1212:9
>        #17 0x72172513 in memory_region_write_accessor softmmu/memory.c:492:5
>        #18 0x72171e51 in access_with_adjusted_size softmmu/memory.c:554:18
>        #19 0x72170766 in memory_region_dispatch_write softmmu/memory.c:1504:16
>        #20 0x721419ee in flatview_write_continue softmmu/physmem.c:2812:23
>        #21 0x721301eb in flatview_write softmmu/physmem.c:2854:12
>        #22 0x7212fca8 in address_space_write softmmu/physmem.c:2950:18
>        #23 0x721d9a53 in qtest_process_command softmmu/qtest.c:727:9
> 
> A DMA descriptor is previously filled in RAM. An I/O access to the
> device (frames #22 to #16) start the DMA engine (frame #13). The
> engine fetch the descriptor and execute the request, which itself
> accesses the SDHCI I/O registers (frame #1 and #0), triggering a
> re-entrancy issue.
> 
> Fix by prohibit transactions from the DMA to devices. The DMA engine
> is thus restricted to memories.
> 
> Reported-by: OSS-Fuzz (Issue 36391)
> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/451
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
>   hw/sd/sdhci.c | 5 +++--
>   1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/hw/sd/sdhci.c b/hw/sd/sdhci.c
> index fe2f21f0c37..0e5e988927e 100644
> --- a/hw/sd/sdhci.c
> +++ b/hw/sd/sdhci.c
> @@ -741,6 +741,7 @@ static void sdhci_do_adma(SDHCIState *s)
>   {
>       unsigned int begin, length;
>       const uint16_t block_size = s->blksize & BLOCK_SIZE_MASK;
> +    const MemTxAttrs attrs = { .memory = true };
>       ADMADescr dscr = {};
>       MemTxResult res;
>       int i;
> @@ -794,7 +795,7 @@ static void sdhci_do_adma(SDHCIState *s)
>                       res = dma_memory_write(s->dma_as, dscr.addr,
>                                              &s->fifo_buffer[begin],
>                                              s->data_count - begin,
> -                                           MEMTXATTRS_UNSPECIFIED);
> +                                           attrs);
>                       if (res != MEMTX_OK) {
>                           break;
>                       }
> @@ -823,7 +824,7 @@ static void sdhci_do_adma(SDHCIState *s)
>                       res = dma_memory_read(s->dma_as, dscr.addr,
>                                             &s->fifo_buffer[begin],
>                                             s->data_count - begin,
> -                                          MEMTXATTRS_UNSPECIFIED);
> +                                          attrs);
>                       if (res != MEMTX_OK) {
>                           break;
>                       }

Looks sane to me!

Reviewed-by: Thomas Huth <thuth@redhat.com>



  parent reply	other threads:[~2022-03-18 18:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 20:56 [RFC PATCH 0/3] hw/sd/sdhci: Fix DMA re-entrancy issue Philippe Mathieu-Daudé
2021-12-15 20:56 ` [RFC PATCH 1/3] hw/sd/sdhci: Honor failed DMA transactions Philippe Mathieu-Daudé
2022-03-18 18:35   ` Thomas Huth
2021-12-15 20:56 ` [RFC PATCH 2/3] hw/sd/sdhci: Prohibit DMA accesses to devices Philippe Mathieu-Daudé
2021-12-16  3:14   ` Jason Wang
2022-03-18 18:38   ` Thomas Huth [this message]
2021-12-15 20:56 ` [RFC PATCH 3/3] tests/qtest/fuzz-sdcard-test: Add reproducer for OSS-Fuzz (Issue 29225) Philippe Mathieu-Daudé
2022-01-18 12:41   ` 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=cdf34ed8-a6bc-946f-a254-4b736fff3ff1@redhat.com \
    --to=thuth@redhat.com \
    --cc=Qiuhao.Li@outlook.com \
    --cc=alxndr@bu.edu \
    --cc=bin.meng@windriver.com \
    --cc=bsd@redhat.com \
    --cc=darren.kenny@oracle.com \
    --cc=david@redhat.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=f4bug@amsat.org \
    --cc=jasowang@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=liq3ea@gmail.com \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=peterx@redhat.com \
    --cc=philippe.mathieu.daude@gmail.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).