From: patchwork-bot+netdevbpf@kernel.org
To: Fang Xieyan <fangxy@xiaopeng.com>
Cc: jhs@mojatatu.com, jiri@resnulli.us, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, eyal.birger@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, liuwb@xiaopeng.com,
zhugl3@xiaopeng.com
Subject: Re: [PATCH] net: sched: em_ipt: validate hook value from netlink
Date: Wed, 28 Oct 2026 11:50:04 +0000 [thread overview]
Message-ID: <179318820432.674732.3698525593677079612.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261026090717.41597-1-fangxy@xiaopeng.com>
Hello:
This patch was applied to netdev/net.git (main)
by Dave Miller <davem@davem-thinkpadp1gen8.ibmlond.csb>:
On Mon, 26 Oct 2026 17:07:17 +0800 you wrote:
> em_ipt_change() accepts the user-provided TCA_EM_IPT_HOOK value
> without validating its range.
>
> The value is later used in check_match() as "1 << im->hook". A hook
> value of 32 or greater causes undefined behavior and may undermine the
> xt match hook-mask validation. The value is also passed to
> nf_hook_state_init() as a hook index.
>
> [...]
Here is the summary with links:
- net: sched: em_ipt: validate hook value from netlink
https://git.kernel.org/netdev/net/c/94cea342e891
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-10-28 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 9:07 [PATCH] net: sched: em_ipt: validate hook value from netlink Fang Xieyan
2026-10-26 9:10 ` netdev-bot+sinfo
2026-10-26 9:30 ` Fang Xieyan
2026-10-28 11: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=179318820432.674732.3698525593677079612.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=eyal.birger@gmail.com \
--cc=fangxy@xiaopeng.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuwb@xiaopeng.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=zhugl3@xiaopeng.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