From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: martin.lau@linux.dev, bpf@vger.kernel.org,
netdev@vger.kernel.org, dddddd@hust.edu.cn,
M202472210@hust.edu.cn, dzm91@hust.edu.cn
Subject: Re: [PATCH bpf] bpf: Reject negative head_room in __bpf_skb_change_head
Date: Tue, 28 Oct 2025 22:20:05 +0000 [thread overview]
Message-ID: <176169000576.2404988.18143767699290680049.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251023125532.182262-1-daniel@iogearbox.net>
Hello:
This patch was applied to bpf/bpf.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Thu, 23 Oct 2025 14:55:32 +0200 you wrote:
> Yinhao et al. recently reported:
>
> Our fuzzing tool was able to create a BPF program which triggered
> the below BUG condition inside pskb_expand_head.
>
> [ 23.016047][T10006] kernel BUG at net/core/skbuff.c:2232!
> [...]
> [ 23.017301][T10006] RIP: 0010:pskb_expand_head+0x1519/0x1530
> [...]
> [ 23.021249][T10006] Call Trace:
> [ 23.021387][T10006] <TASK>
> [ 23.021507][T10006] ? __pfx_pskb_expand_head+0x10/0x10
> [ 23.021725][T10006] __bpf_skb_change_head+0x22a/0x520
> [ 23.021939][T10006] bpf_skb_change_head+0x34/0x1b0
> [ 23.022143][T10006] ___bpf_prog_run+0xf70/0xb670
> [ 23.022342][T10006] __bpf_prog_run32+0xed/0x140
> [...]
>
> [...]
Here is the summary with links:
- [bpf] bpf: Reject negative head_room in __bpf_skb_change_head
https://git.kernel.org/bpf/bpf/c/2cbb259ec4f8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-10-28 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 12:55 [PATCH bpf] bpf: Reject negative head_room in __bpf_skb_change_head Daniel Borkmann
2025-10-28 22:20 ` 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=176169000576.2404988.18143767699290680049.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=M202472210@hust.edu.cn \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dddddd@hust.edu.cn \
--cc=dzm91@hust.edu.cn \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.