All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Qiang <liq3ea@gmail.com>
To: P J P <ppandit@redhat.com>
Cc: Prasad J Pandit <pjp@fedoraproject.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Yi Ren <yunye.ry@alibaba-inc.com>,
	Yongkang Jia <j_kangel@163.com>, Gaoning Pan <pgn@zju.edu.cn>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH] hw: usb: hcd-ohci: check len and frame_number variables
Date: Fri, 11 Sep 2020 22:57:45 +0800	[thread overview]
Message-ID: <CAKXe6SLFG1XMCw7yNM3bres29jiqJ5oLpJUgzXGjj8ay=NkwHQ@mail.gmail.com> (raw)
In-Reply-To: <20200911122703.126696-1-ppandit@redhat.com>

P J P <ppandit@redhat.com> 于2020年9月11日周五 下午8:30写道:
>
> From: Prasad J Pandit <pjp@fedoraproject.org>
>
> While servicing the OHCI transfer descriptors(TD), OHCI host
> controller derives variables 'start_addr', 'end_addr', 'len'
> etc. from values supplied by the host controller driver.
> Host controller driver may supply values such that using
> above variables leads to out-of-bounds access or loop issues.
> Add checks to avoid them.
>
> AddressSanitizer: stack-buffer-overflow on address 0x7ffd53af76a0
>   READ of size 2 at 0x7ffd53af76a0 thread T0
>   #0 ohci_service_iso_td ../hw/usb/hcd-ohci.c:734
>   #1 ohci_service_ed_list ../hw/usb/hcd-ohci.c:1180
>   #2 ohci_process_lists ../hw/usb/hcd-ohci.c:1214
>   #3 ohci_frame_boundary ../hw/usb/hcd-ohci.c:1257
>   #4 timerlist_run_timers ../util/qemu-timer.c:572
>   #5 qemu_clock_run_timers ../util/qemu-timer.c:586
>   #6 qemu_clock_run_all_timers ../util/qemu-timer.c:672
>   #7 main_loop_wait ../util/main-loop.c:527
>   #8 qemu_main_loop ../softmmu/vl.c:1676
>   #9 main ../softmmu/main.c:50
>

Hello Prasad,
Could you also provide the reproducer?

> Reported-by: Gaoning Pan <pgn@zju.edu.cn>
> Reported-by: Yongkang Jia <j_kangel@163.com>
> Reported-by: Yi Ren <yunye.ry@alibaba-inc.com>
> Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org>
> ---
>  hw/usb/hcd-ohci.c | 29 +++++++++++++++++++++++++++--
>  1 file changed, 27 insertions(+), 2 deletions(-)
>
> diff --git a/hw/usb/hcd-ohci.c b/hw/usb/hcd-ohci.c
> index 1e6e85e86a..76fb9282e3 100644
> --- a/hw/usb/hcd-ohci.c
> +++ b/hw/usb/hcd-ohci.c
> @@ -691,6 +691,11 @@ static int ohci_service_iso_td(OHCIState *ohci, struct ohci_ed *ed,
>             the next ISO TD of the same ED */
>          trace_usb_ohci_iso_td_relative_frame_number_big(relative_frame_number,
>                                                          frame_count);
> +        if (OHCI_CC_DATAOVERRUN == OHCI_BM(iso_td.flags, TD_CC)) {
> +            /* avoid infinite loop */
> +            return 1;
> +        }

I think it is better to split this patch to 2 or three as the infinite
loop as the buffer overflow are independent.

1. here the infinite loop

> +
>          OHCI_SET_BM(iso_td.flags, TD_CC, OHCI_CC_DATAOVERRUN);
>          ed->head &= ~OHCI_DPTR_MASK;
>          ed->head |= (iso_td.next & OHCI_DPTR_MASK);
> @@ -731,7 +736,11 @@ static int ohci_service_iso_td(OHCIState *ohci, struct ohci_ed *ed,
>      }
>
>      start_offset = iso_td.offset[relative_frame_number];
> -    next_offset = iso_td.offset[relative_frame_number + 1];
> +    if (relative_frame_number < frame_count) {
> +        next_offset = iso_td.offset[relative_frame_number + 1];
> +    } else {
> +        next_offset = iso_td.be;
> +    }

2. here the stack buffer overflow

>
>      if (!(OHCI_BM(start_offset, TD_PSW_CC) & 0xe) ||
>          ((relative_frame_number < frame_count) &&
> @@ -764,7 +773,12 @@ static int ohci_service_iso_td(OHCIState *ohci, struct ohci_ed *ed,
>          }
>      } else {
>          /* Last packet in the ISO TD */
> -        end_addr = iso_td.be;
> +        end_addr = next_offset;
> +    }
> +
> +    if (start_addr > end_addr) {
> +        trace_usb_ohci_iso_td_bad_cc_overrun(start_addr, end_addr);
> +        return 1;
>      }
>
>      if ((start_addr & OHCI_PAGE_MASK) != (end_addr & OHCI_PAGE_MASK)) {
> @@ -773,6 +787,9 @@ static int ohci_service_iso_td(OHCIState *ohci, struct ohci_ed *ed,
>      } else {
>          len = end_addr - start_addr + 1;
>      }
> +    if (len > sizeof(ohci->usb_buf)) {
> +        len = sizeof(ohci->usb_buf);
> +    }
>
>      if (len && dir != OHCI_TD_DIR_IN) {
>          if (ohci_copy_iso_td(ohci, start_addr, end_addr, ohci->usb_buf, len,
> @@ -975,8 +992,16 @@ static int ohci_service_td(OHCIState *ohci, struct ohci_ed *ed)
>          if ((td.cbp & 0xfffff000) != (td.be & 0xfffff000)) {
>              len = (td.be & 0xfff) + 0x1001 - (td.cbp & 0xfff);
>          } else {
> +            if (td.cbp > td.be) {
> +                trace_usb_ohci_iso_td_bad_cc_overrun(td.cbp, td.be);
> +                ohci_die(ohci);
> +                return 1;
> +            }
>              len = (td.be - td.cbp) + 1;
>          }
> +        if (len > sizeof(ohci->usb_buf)) {
> +            len = sizeof(ohci->usb_buf);
> +        }
>

3. Then here is the heap overflow.


So I think it can be more easier to review to split this to 3 patches.

Thanks,
Li Qiang

>          pktlen = len;
>          if (len && dir != OHCI_TD_DIR_IN) {
> --
> 2.26.2
>
>


  reply	other threads:[~2020-09-11 14:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11 12:27 [PATCH] hw: usb: hcd-ohci: check len and frame_number variables P J P
2020-09-11 14:57 ` Li Qiang [this message]
2020-09-11 19:20   ` Alexander Bulekov
2020-09-12  1:48     ` Alexander Bulekov
2020-09-15  6:47       ` P J P

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='CAKXe6SLFG1XMCw7yNM3bres29jiqJ5oLpJUgzXGjj8ay=NkwHQ@mail.gmail.com' \
    --to=liq3ea@gmail.com \
    --cc=j_kangel@163.com \
    --cc=kraxel@redhat.com \
    --cc=pgn@zju.edu.cn \
    --cc=pjp@fedoraproject.org \
    --cc=ppandit@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yunye.ry@alibaba-inc.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 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.