netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chenyuan Yang <chenyuan0y@gmail.com>
To: Eric Dumazet <edumazet@google.com>
Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
	 davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	 netdev@vger.kernel.org, zzjas98@gmail.com
Subject: Re: [net/sched] Question about possible misuse checksum in tcf_csum_ipv6_icmp()
Date: Mon, 18 Mar 2024 14:54:30 -0500	[thread overview]
Message-ID: <CALGdzuoBH+3B=9m_Fif7-+auGUsD6CUDqRDMbc2RMHVuhu2XPw@mail.gmail.com> (raw)
In-Reply-To: <CANn89iKjdynvAddoWrQ-Akm=fQeHD9Ww=rAwfGCmYMDSRk6iJw@mail.gmail.com>

Thank you very much for your swift response.

> It seems we have proper pskb_may_pull() calls.
I realized that I had overlooked verifying the suitability of the SKB
in this context. Your observation is indeed correct, and I now
understand that this should not present any concerns.

Thank you once again for your valuable feedback.

Best,
Chenyuan

On Mon, Mar 18, 2024 at 2:46 PM Eric Dumazet <edumazet@google.com> wrote:
>
> On Mon, Mar 18, 2024 at 8:31 PM Chenyuan Yang <chenyuan0y@gmail.com> wrote:
> >
> > Dear TC subsystem maintainers,
> >
> > We are curious whether the function `tcf_csum_ipv6_icmp()` would have a misuse of `csum_partial()` leading to an out-of-bounds access.
> >
> > The function `tcf_csum_ipv6_icmp` is https://elixir.bootlin.com/linux/v6.8/source/net/sched/act_csum.c#L183 and the relevant code is
> > ```
> > static int tcf_csum_ipv6_icmp(struct sk_buff *skb, unsigned int ihl,
> >                               unsigned int ipl)
> > {
> >   ...
> >         ip6h = ipv6_hdr(skb);
> >         icmp6h->icmp6_cksum = 0;
> >         skb->csum = csum_partial(icmp6h, ipl - ihl, 0);
> >         icmp6h->icmp6_cksum = csum_ipv6_magic(&ip6h->saddr, &ip6h->daddr,
> >                                               ipl - ihl, IPPROTO_ICMPV6,
> >                                               skb->csum);
> >   ...
> > }
> > ```
> >
> > Based on this patch: https://lore.kernel.org/netdev/20240201083817.12774-1-atenart@kernel.org/T/, it seems that the `skb` here for ICMPv6 could be non-linear, and `csum_partial` is not suitable for non-linear SKBs, which could lead to an out-of-bound access. The correct approach is to use `skb_checksum` which properly handles non-linear SKBs.
> >
> > Based on the above information, a possible fix would be
> > ```
> > -       skb->csum = csum_partial(icmp6h, ipl - ihl, 0);
> > +       skb->csum = skb_checksum(skb, skb_transport_offset(skb), ipl - ihl, 0);
> > ```
>
> Why would this code be an issue only in  tcf_csum_ipv6_icmp(), and not
> in other functions ?
>
> It seems we have proper pskb_may_pull() calls.
>
> If you have a syzbot/syzkaller trace, please share it.

      reply	other threads:[~2024-03-18 19:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-18 19:31 [net/sched] Question about possible misuse checksum in tcf_csum_ipv6_icmp() Chenyuan Yang
2024-03-18 19:46 ` Eric Dumazet
2024-03-18 19:54   ` Chenyuan Yang [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='CALGdzuoBH+3B=9m_Fif7-+auGUsD6CUDqRDMbc2RMHVuhu2XPw@mail.gmail.com' \
    --to=chenyuan0y@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=xiyou.wangcong@gmail.com \
    --cc=zzjas98@gmail.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).