From: Florian Westphal <fw@strlen.de>
To: "Fengtao (fengtao, Euler)" <fengtao40@huawei.com>
Cc: Florian Westphal <fw@strlen.de>,
jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
davem@davemloft.net, kuba@kernel.org, stephen@networkplumber.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
yanan@huawei.com, caowangbao@huawei.com
Subject: Re: BUG: KASAN: stack-out-of-bounds in __ip_options_echo
Date: Fri, 5 May 2023 07:58:22 +0200 [thread overview]
Message-ID: <20230505055822.GA6126@breakpoint.cc> (raw)
In-Reply-To: <9dd7ec8f-bc40-39af-febb-a7e8aabbaaed@huawei.com>
Fengtao (fengtao, Euler) <fengtao40@huawei.com> wrote:
> Hi
>
> I have tested the patch, the panic not happend.
> And I search the similar issue in kernel, and found commit:
> [1]https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ed0de45a1008
> [2]https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3da1ed7ac398
>
> So I tested another patch like this:
> ------------[ cut here ]------------
> --- .//net/ipv4/netfilter/nf_reject_ipv4.c 2023-05-02 13:03:35.427896081 +0000
> +++ .//net/ipv4/netfilter/nf_reject_ipv4.c.new 2023-05-02 13:03:00.433897970 +0000
> @@ -187,6 +187,7 @@ >
> void nf_send_unreach(struct sk_buff *skb_in, int code, int hook)
> {
> + struct ip_options opt;
> struct iphdr *iph = ip_hdr(skb_in);
> u8 proto = iph->protocol;
>
> @@ -196,13 +197,18 @@
> if (hook == NF_INET_PRE_ROUTING && nf_reject_fill_skb_dst(skb_in))
> return;
>
> + memset(&opt, 0, sizeof(opt));
> + opt.optlen = iph->ihl*4 - sizeof(struct iphdr);
> + if (__ip_options_compile(dev_net(skb_in->dev), &opt, skb_in, NULL))
> + return;
> +
> if (skb_csum_unnecessary(skb_in) || !nf_reject_verify_csum(proto)) {
> - icmp_send(skb_in, ICMP_DEST_UNREACH, code, 0);
> + __icmp_send(skb_in, ICMP_DEST_UNREACH, code, 0, &opt);
> return;
> }
>
> if (nf_ip_checksum(skb_in, hook, ip_hdrlen(skb_in), proto) == 0)
> - icmp_send(skb_in, ICMP_DEST_UNREACH, code, 0);
> + __icmp_send(skb_in, ICMP_DEST_UNREACH, code, 0, &opt);
> }
> EXPORT_SYMBOL_GPL(nf_send_unreach);
> ------------[ cut here ]------------
>
> This can also fix the issue :)
No, it papers over the problem, by only fixing this specific instance
(icmpv4). What about ipv6? What about all other IPCB accesses?
> BTW, I think the problem is more then ipvlan? Maybe some other scenarios that can trigger such issue.
Such as?
I don't see how this is fixable, just have have a look at "git grep
IPCB", how do you envision stack to know how such access is valid or
not?
next prev parent reply other threads:[~2023-05-05 5:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 11:49 BUG: KASAN: stack-out-of-bounds in __ip_options_echo Fengtao (fengtao, Euler)
2023-05-02 16:54 ` Florian Westphal
2023-05-04 7:33 ` Fengtao (fengtao, Euler)
2023-05-05 5:58 ` Florian Westphal [this message]
2023-05-06 3:01 ` Fengtao (fengtao, Euler)
2023-05-06 17:18 ` Florian Westphal
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=20230505055822.GA6126@breakpoint.cc \
--to=fw@strlen.de \
--cc=caowangbao@huawei.com \
--cc=davem@davemloft.net \
--cc=fengtao40@huawei.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=xiyou.wangcong@gmail.com \
--cc=yanan@huawei.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).