From: patchwork-bot+netdevbpf@kernel.org
To: Greg KH <gregkh@linuxfoundation.org>
Cc: netdev@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, petkan@nucleusys.com,
stable@kernel.org
Subject: Re: [PATCH net] net: usb: pegasus: validate USB endpoints
Date: Thu, 26 Feb 2026 03:00:07 +0000 [thread overview]
Message-ID: <177207480729.1011529.13653045267962557562.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <2026022347-legibly-attest-cc5c@gregkh>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 23 Feb 2026 13:58:48 +0100 you wrote:
> The pegasus driver should validate that the device it is probing has the
> proper number and types of USB endpoints it is expecting before it binds
> to it. If a malicious device were to not have the same urbs the driver
> will crash later on when it blindly accesses these endpoints.
>
> Cc: Petko Manolov <petkan@nucleusys.com>
> Cc: stable <stable@kernel.org>
> Assisted-by: gkh_clanker_2000
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> [...]
Here is the summary with links:
- [net] net: usb: pegasus: validate USB endpoints
https://git.kernel.org/netdev/net/c/11de1d3ae556
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-02-26 3:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 12:58 [PATCH net] net: usb: pegasus: validate USB endpoints Greg Kroah-Hartman
2026-02-23 14:39 ` Alan Stern
2026-02-23 14:54 ` Greg Kroah-Hartman
2026-02-23 15:02 ` Alan Stern
2026-02-26 3:00 ` 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=177207480729.1011529.13653045267962557562.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=petkan@nucleusys.com \
--cc=stable@kernel.org \
/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.