From: patchwork-bot+netdevbpf@kernel.org
To: Deepanshu Kartikey <kartikey406@gmail.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, khalasa@piap.pl,
andriy.shevchenko@linux.intel.com, o.rempel@pengutronix.de,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+3d43c9066a5b54902232@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] net: usb: asix: validate PHY address before use
Date: Sun, 28 Dec 2025 08:31:38 +0000 [thread overview]
Message-ID: <176691069878.2288022.11429668150024259840.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251218011156.276824-1-kartikey406@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 18 Dec 2025 06:41:56 +0530 you wrote:
> The ASIX driver reads the PHY address from the USB device via
> asix_read_phy_addr(). A malicious or faulty device can return an
> invalid address (>= PHY_MAX_ADDR), which causes a warning in
> mdiobus_get_phy():
>
> addr 207 out of range
> WARNING: drivers/net/phy/mdio_bus.c:76
>
> [...]
Here is the summary with links:
- [v2] net: usb: asix: validate PHY address before use
https://git.kernel.org/netdev/net/c/a1e077a3f76e
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-12-28 8:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 1:11 [PATCH v2] net: usb: asix: validate PHY address before use Deepanshu Kartikey
2025-12-18 10:17 ` Andrew Lunn
2025-12-28 8:31 ` 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=176691069878.2288022.11429668150024259840.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andriy.shevchenko@linux.intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kartikey406@gmail.com \
--cc=khalasa@piap.pl \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=syzbot+3d43c9066a5b54902232@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).