From: Jason Wang <jasowang@redhat.com>
Cc: Alexander Bulekov <alxndr@bu.edu>,
Cheolwoo Myung <cwmyung@snu.ac.kr>,
Ruhr-University Bochum <bugs-syssec@rub.de>,
qemu-devel@nongnu.org, Prasad J Pandit <ppandit@redhat.com>
Subject: Re: [PATCH] e1000: fail early for evil descriptor
Date: Fri, 26 Feb 2021 15:05:06 +0800 [thread overview]
Message-ID: <3f0bccce-3cae-e0d6-6268-7616206db30d@redhat.com> (raw)
In-Reply-To: <20210224054528.491866-1-jasowang@redhat.com>
On 2021/2/24 1:45 下午, Jason Wang wrote:
> During procss_tx_desc(), driver can try to chain data descriptor with
> legacy descriptor, when will lead underflow for the following
> calculation in process_tx_desc() for bytes:
>
> if (tp->size + bytes > msh)
> bytes = msh - tp->size;
>
> This will lead a infinite loop. So check and fail early if tp->size if
> greater or equal to msh.
>
> Reported-by: Alexander Bulekov <alxndr@bu.edu>
> Reported-by: Cheolwoo Myung <cwmyung@snu.ac.kr>
> Reported-by: Ruhr-University Bochum <bugs-syssec@rub.de>
> Cc: Prasad J Pandit <ppandit@redhat.com>
> Signed-off-by: Jason Wang <jasowang@redhat.com>
> ---
> hw/net/e1000.c | 4 ++++
> 1 file changed, 4 insertions(+)
Applied.
Thanks
>
> diff --git a/hw/net/e1000.c b/hw/net/e1000.c
> index d8da2f6528..4345d863e6 100644
> --- a/hw/net/e1000.c
> +++ b/hw/net/e1000.c
> @@ -670,6 +670,9 @@ process_tx_desc(E1000State *s, struct e1000_tx_desc *dp)
> msh = tp->tso_props.hdr_len + tp->tso_props.mss;
> do {
> bytes = split_size;
> + if (tp->size >= msh) {
> + goto eop;
> + }
> if (tp->size + bytes > msh)
> bytes = msh - tp->size;
>
> @@ -695,6 +698,7 @@ process_tx_desc(E1000State *s, struct e1000_tx_desc *dp)
> tp->size += split_size;
> }
>
> +eop:
> if (!(txd_lower & E1000_TXD_CMD_EOP))
> return;
> if (!(tp->cptse && tp->size < tp->tso_props.hdr_len)) {
prev parent reply other threads:[~2021-02-26 7:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 5:45 [PATCH] e1000: fail early for evil descriptor Jason Wang
2021-02-26 7:05 ` Jason Wang [this message]
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=3f0bccce-3cae-e0d6-6268-7616206db30d@redhat.com \
--to=jasowang@redhat.com \
--cc=alxndr@bu.edu \
--cc=bugs-syssec@rub.de \
--cc=cwmyung@snu.ac.kr \
--cc=ppandit@redhat.com \
--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 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).