From: patchwork-bot+netdevbpf@kernel.org
To: Nikita Zhandarovich <n.zhandarovich@fintech.ru>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+d693c07c6f647e0388d3@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com, lvc-project@linuxtesting.org
Subject: Re: [PATCH net] usbnet: gl620a: fix endpoint checking in genelink_bind()
Date: Thu, 27 Feb 2025 10:50:29 +0000 [thread overview]
Message-ID: <174065342951.1379797.16119885160230991674.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250224172919.1220522-1-n.zhandarovich@fintech.ru>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 24 Feb 2025 20:29:17 +0300 you wrote:
> Syzbot reports [1] a warning in usb_submit_urb() triggered by
> inconsistencies between expected and actually present endpoints
> in gl620a driver. Since genelink_bind() does not properly
> verify whether specified eps are in fact provided by the device,
> in this case, an artificially manufactured one, one may get a
> mismatch.
>
> [...]
Here is the summary with links:
- [net] usbnet: gl620a: fix endpoint checking in genelink_bind()
https://git.kernel.org/netdev/net/c/1cf9631d836b
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:[~2025-02-27 10:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 17:29 [PATCH net] usbnet: gl620a: fix endpoint checking in genelink_bind() Nikita Zhandarovich
2025-02-27 10: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=174065342951.1379797.16119885160230991674.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=n.zhandarovich@fintech.ru \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+d693c07c6f647e0388d3@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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