public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kees Cook <keescook@chromium.org>
Cc: kuba@kernel.org,
	syzbot+fda18eaa8c12534ccb3b@syzkaller.appspotmail.com,
	edumazet@google.com, davem@davemloft.net, pabeni@redhat.com,
	asml.silence@gmail.com, soopthegoop@gmail.com, vbabka@suse.cz,
	kasan-dev@googlegroups.com, andrii@kernel.org, ast@kernel.org,
	bpf@vger.kernel.org, daniel@iogearbox.net, haoluo@google.com,
	hawk@kernel.org, john.fastabend@gmail.com, jolsa@kernel.org,
	kpsingh@kernel.org, martin.lau@linux.dev, sdf@google.com,
	song@kernel.org, yhs@fb.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, rmody@marvell.com,
	aelior@marvell.com, manishc@marvell.com, imagedong@tencent.com,
	dsahern@kernel.org, richardbgobert@gmail.com,
	andreyknvl@gmail.com, rientjes@google.com,
	GR-Linux-NIC-Dev@marvell.com, linux-hardening@vger.kernel.org
Subject: Re: [PATCH net-next v3] skbuff: Introduce slab_build_skb()
Date: Sat, 10 Dec 2022 04:00:18 +0000	[thread overview]
Message-ID: <167064481825.12189.4717731779203655380.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221208060256.give.994-kees@kernel.org>

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Wed,  7 Dec 2022 22:02:59 -0800 you wrote:
> syzkaller reported:
> 
>   BUG: KASAN: slab-out-of-bounds in __build_skb_around+0x235/0x340 net/core/skbuff.c:294
>   Write of size 32 at addr ffff88802aa172c0 by task syz-executor413/5295
> 
> For bpf_prog_test_run_skb(), which uses a kmalloc()ed buffer passed to
> build_skb().
> 
> [...]

Here is the summary with links:
  - [net-next,v3] skbuff: Introduce slab_build_skb()
    https://git.kernel.org/netdev/net-next/c/ce098da1497c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-12-10  4:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08  6:02 [PATCH net-next v3] skbuff: Introduce slab_build_skb() Kees Cook
2022-12-08  8:13 ` Vlastimil Babka
2022-12-08 10:19   ` Feng Tang
2022-12-08 11:08     ` Vlastimil Babka
2022-12-10  4:00 ` patchwork-bot+netdevbpf [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=167064481825.12189.4717731779203655380.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=GR-Linux-NIC-Dev@marvell.com \
    --cc=aelior@marvell.com \
    --cc=andreyknvl@gmail.com \
    --cc=andrii@kernel.org \
    --cc=asml.silence@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=haoluo@google.com \
    --cc=hawk@kernel.org \
    --cc=imagedong@tencent.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kasan-dev@googlegroups.com \
    --cc=keescook@chromium.org \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manishc@marvell.com \
    --cc=martin.lau@linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=richardbgobert@gmail.com \
    --cc=rientjes@google.com \
    --cc=rmody@marvell.com \
    --cc=sdf@google.com \
    --cc=song@kernel.org \
    --cc=soopthegoop@gmail.com \
    --cc=syzbot+fda18eaa8c12534ccb3b@syzkaller.appspotmail.com \
    --cc=vbabka@suse.cz \
    --cc=yhs@fb.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