From: patchwork-bot+netdevbpf@kernel.org
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: netdev@vger.kernel.org, jiri@resnulli.us, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, victor@mojatatu.com, tgraf@suug.ch,
hybris@mojatatu.ai, sashiko-bot@kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net] net/sched: em_text: reject unterminated algo before autoload
Date: Fri, 02 Oct 2026 01:10:05 +0000 [thread overview]
Message-ID: <179090340503.3165918.7074749420466888679.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <QDISC-2DIU.v1.20260929183844@mojatatu.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 30 Sep 2026 03:31:02 -0400 you wrote:
> This is a follow-up to commit 9c572a83037a ("net/sched: fix potential
> stack infoleak in em_text_dump()"), which zero-initialised the dump-side
> struct. Sashiko pointed at a pre-existing bug that exposed the change-side
> input-validation gap open.
>
> em_text_change() casts the raw netlink attribute payload to struct
> tcf_em_text and passes conf->algo, a 16-byte array with no enforced NUL
> terminator, to textsearch_prepare(). On the TS_AUTOLOAD retry
> textsearch_prepare() calls request_module("ts_%s", algo); vsnprintf()
> walks %s until it finds a NUL, so an algo[] with no NUL reads past the
> array into the adjacent struct fields and payload and feeds those bytes
> to the usermode helper command line. This is an out-of-bounds read and
> a kernel memory disclosure.
>
> [...]
Here is the summary with links:
- [net] net/sched: em_text: reject unterminated algo before autoload
https://git.kernel.org/netdev/net/c/c9728fcf2e7f
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-02 1:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 7:31 [PATCH net] net/sched: em_text: reject unterminated algo before autoload Jamal Hadi Salim
2026-10-02 1:10 ` 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=179090340503.3165918.7074749420466888679.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=hybris@mojatatu.ai \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sashiko-bot@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tgraf@suug.ch \
--cc=victor@mojatatu.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