From: David Miller <davem@davemloft.net>
To: bodefang@126.com
Cc: kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org, kuba@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ipv6: Prevent overrun when parsing v6 header options
Date: Mon, 28 Dec 2020 15:03:38 -0800 (PST) [thread overview]
Message-ID: <20201228.150338.187303639465700771.davem@davemloft.net> (raw)
In-Reply-To: <1609078295-4025719-1-git-send-email-bodefang@126.com>
From: Defang Bo <bodefang@126.com>
Date: Sun, 27 Dec 2020 22:11:35 +0800
> Similar to commit<2423496af35>, the fragmentation code tries to parse the header options in order
> to figure out where to insert the fragment option. Since nexthdr points
> to an invalid option, the calculation of the size of the network header
> can made to be much larger than the linear section of the skb and data
> is read outside of it.
>
> Signed-off-by: Defang Bo <bodefang@126.com>
Could you please repost this with a proper Fixes: tag, thank you.
next prev parent reply other threads:[~2020-12-28 23:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-27 14:11 [PATCH] ipv6: Prevent overrun when parsing v6 header options Defang Bo
2020-12-28 23:03 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-30 15:28 Young Xiao
2019-05-30 17:17 ` Eric Dumazet
2019-05-31 3:04 ` Yang Xiao
2019-05-31 17:35 ` Eric Dumazet
2019-06-04 6:59 ` Yang Xiao
2019-06-04 13:29 ` Eric Dumazet
2019-05-31 6:29 ` Herbert Xu
2019-05-31 14:50 ` Eric Dumazet
2019-05-31 14:54 ` Herbert Xu
2019-05-31 15:57 ` Eric Dumazet
2019-05-31 16:12 ` Yang Xiao
2019-04-12 3:34 Young Xiao
2019-04-17 3:45 ` David Miller
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=20201228.150338.187303639465700771.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bodefang@126.com \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).