From: patchwork-bot+netdevbpf@kernel.org
To: Xinsheng Zhu <xinsheng.zhu.ny@gmail.com>
Cc: netdev@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, rfiler@sierrawireless.com,
epasheva@sierrawireless.com
Subject: Re: [PATCH net] net: usb: sierra_net: reject short firmware attribute reads
Date: Thu, 08 Oct 2026 02:30:10 +0000 [thread overview]
Message-ID: <179142661078.3776717.16561807411140979685.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261005155920.27735-1-xinsheng.zhu.ny@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 5 Oct 2026 11:59:20 -0400 you wrote:
> sierra_net_get_fw_attr() only checks usbnet_read_cmd() for negative
> return values before converting attrdata and storing it in *datap.
> A zero-length or one-byte response leaves attrdata wholly or partially
> uninitialized.
>
> Although sierra_net_bind() rejects responses of unexpected length, its
> dev_dbg() call uses fwattr before that check. When the debug message is
> enabled, the incomplete value may therefore be used in the debug output.
>
> [...]
Here is the summary with links:
- [net] net: usb: sierra_net: reject short firmware attribute reads
https://git.kernel.org/netdev/net-next/c/8df0638138d3
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-08 2:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 15:59 [PATCH net] net: usb: sierra_net: reject short firmware attribute reads Xinsheng Zhu
2026-10-08 2:30 ` 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=179142661078.3776717.16561807411140979685.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=epasheva@sierrawireless.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rfiler@sierrawireless.com \
--cc=xinsheng.zhu.ny@gmail.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