From: Eric Dumazet <eric.dumazet@gmail.com>
To: Alexander Aring <aring@mojatatu.com>, yotam.gi@gmail.com
Cc: jhs@mojatatu.com, davem@davemloft.net, xiyou.wangcong@gmail.com,
jiri@resnulli.us, yuvalm@mellanox.com, netdev@vger.kernel.org,
kernel@mojatatu.com
Subject: Re: [PATCHv2 net 3/3] net: sched: ife: check on metadata length
Date: Thu, 19 Apr 2018 14:50:27 -0700 [thread overview]
Message-ID: <2cd6cb29-ab28-bd99-4fbd-a4f5659e3009@gmail.com> (raw)
In-Reply-To: <20180419214438.6801-4-aring@mojatatu.com>
On 04/19/2018 02:44 PM, Alexander Aring wrote:
> This patch checks if sk buffer is available to dererence ife header. If
> not then NULL will returned to signal an malformed ife packet. This
> avoids to crashing the kernel from outside.
>
> Signed-off-by: Alexander Aring <aring@mojatatu.com>
> Reviewed-by: Yotam Gigi <yotam.gi@gmail.com>
> Acked-by: Jamal Hadi Salim <jhs@mojatatu.com>
> ---
> net/ife/ife.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/net/ife/ife.c b/net/ife/ife.c
> index 7fbe70a0af4b..93e8c36ce6ec 100644
> --- a/net/ife/ife.c
> +++ b/net/ife/ife.c
> @@ -70,6 +70,9 @@ void *ife_decode(struct sk_buff *skb, u16 *metalen)
> u16 ifehdrln;
>
> ifehdr = (struct ifeheadr *) (skb->data + skb->dev->hard_header_len);
> + if (skb->len < skb->dev->hard_header_len + IFE_METAHDRLEN)
> + return NULL;
> +
> ifehdrln = ntohs(ifehdr->metalen);
> total_pull = skb->dev->hard_header_len + ifehdrln;
>
>
Nope, please use pskb_may_pull()
prev parent reply other threads:[~2018-04-19 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 21:44 [PATCHv2 net 0/3] net: sched: ife: malformed ife packet fixes Alexander Aring
2018-04-19 21:44 ` [PATCHv2 net 1/3] net: sched: ife: signal not finding metaid Alexander Aring
2018-04-19 21:44 ` [PATCHv2 net 2/3] net: sched: ife: handle malformed tlv length Alexander Aring
2018-04-19 21:44 ` [PATCHv2 net 3/3] net: sched: ife: check on metadata length Alexander Aring
2018-04-19 21:50 ` Eric Dumazet [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=2cd6cb29-ab28-bd99-4fbd-a4f5659e3009@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=aring@mojatatu.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kernel@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
--cc=yotam.gi@gmail.com \
--cc=yuvalm@mellanox.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).