From: patchwork-bot+netdevbpf@kernel.org
To: Wei Jie Law <law.wei.jie@gt.tech.gov.sg>
Cc: petkan@nucleusys.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, 98lawweijie@gmail.com
Subject: Re: [PATCH net v2 0/2] net: usb: pegasus: fix receive length handling
Date: Mon, 26 Oct 2026 23:20:06 +0000 [thread overview]
Message-ID: <179305680682.3450824.8798469906798497439.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261021020310.34045-1-law.wei.jie@gt.tech.gov.sg>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 21 Oct 2026 10:03:08 +0800 you wrote:
> Two fixes for read_bulk_callback(), both reachable by a USB device that
> identifies itself as a Pegasus II adapter.
>
> Patch 1 fixes an out-of-bounds write: on the 0x8513, every frame that
> is dropped because of an oversized length field advances the receive
> buffer by two bytes, until the host controller writes past the end of
> the skb data area.
>
> [...]
Here is the summary with links:
- [net,v2,1/2] net: usb: pegasus: do not advance rx_skb->data on dropped frames
https://git.kernel.org/netdev/net/c/bfa09dccf98c
- [net,v2,2/2] net: usb: pegasus: check rx pkt_len against the received length
https://git.kernel.org/netdev/net/c/efee699f6de0
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-26 23:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 2:03 [PATCH net v2 0/2] net: usb: pegasus: fix receive length handling Wei Jie Law
2026-10-21 2:03 ` [PATCH net v2 1/2] net: usb: pegasus: do not advance rx_skb->data on dropped frames Wei Jie Law
2026-10-21 2:08 ` sashiko-bot
2026-10-26 16:31 ` Simon Horman
2026-10-21 2:03 ` [PATCH net v2 2/2] net: usb: pegasus: check rx pkt_len against the received length Wei Jie Law
2026-10-21 2:08 ` sashiko-bot
2026-10-26 16:31 ` Simon Horman
2026-10-26 23: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=179305680682.3450824.8798469906798497439.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=98lawweijie@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=law.wei.jie@gt.tech.gov.sg \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petkan@nucleusys.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.