From: patchwork-bot+netdevbpf@kernel.org
To: Gris Ge <cnfourt@gmail.com>
Cc: dsahern@kernel.org, idosch@nvidia.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
stable@vger.kernel.org, horms@kernel.org, kees@kernel.org,
gustavoars@kernel.org, cratiu@nvidia.com, gal@nvidia.com,
tariqt@nvidia.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH net v2] net: ip_tunnel: initialize `options_len` before referencing options
Date: Wed, 16 Sep 2026 00:50:04 +0000 [thread overview]
Message-ID: <178951980439.2341174.3543067231110573907.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260913090851.468216-1-cnfourt@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 13 Sep 2026 17:08:50 +0800 you wrote:
> The following command triggers a kernel panic:
>
> ip link add d0 type dummy; ip link set d0 up
> ip route add 10.30.0.0/16 \
> encap ip id 300 geneve_opts 4660:66:11223344 dev d0
>
> memcpy: detected buffer overflow: 4 byte write of buffer size 0
> kernel BUG at lib/string_helpers.c:1044!
> ...
> ip_tun_parse_opts.part.0.cold+0x10/0x10
> ip_tun_build_state+0x116/0x2a0
>
> [...]
Here is the summary with links:
- [net,v2] net: ip_tunnel: initialize `options_len` before referencing options
https://git.kernel.org/netdev/net/c/455ebeadf714
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:[~2026-09-16 0:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 9:08 [PATCH net v2] net: ip_tunnel: initialize `options_len` before referencing options Gris Ge
2026-09-14 1:35 ` Hangbin Liu
2026-09-14 5:42 ` Gustavo A. R. Silva
2026-09-16 0:50 ` 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=178951980439.2341174.3543067231110573907.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cnfourt@gmail.com \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=gustavoars@kernel.org \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tariqt@nvidia.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 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.