From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Quan Sun <2022090917019@std.uestc.edu.cn>,
netdev@vger.kernel.org, andrew@lunn.ch
Cc: kuba@kernel.org, edumazet@google.com, pabeni@redhat.com
Subject: Re: [PATCH net v2] net: ethtool: fix NULL pointer dereference in phy_reply_size
Date: Thu, 7 May 2026 17:39:57 +0200 [thread overview]
Message-ID: <329ee928-2694-4348-a6f7-099618081dde@bootlin.com> (raw)
In-Reply-To: <20260507131738.1173835-1-2022090917019@std.uestc.edu.cn>
Hi,
On 07/05/2026 15:17, Quan Sun wrote:
> In phy_prepare_data(), several strings such as 'name', 'drvname',
> 'upstream_sfp_name', and 'downstream_sfp_name' are allocated using
> kstrdup(). However, these allocations were not checked for failure.
>
> If kstrdup() fails for 'name', it returns NULL while the function
> continues. This leads to a kernel NULL pointer dereference and panic
> later in phy_reply_size() when it unconditionally calls strlen() on
> the NULL pointer.
>
> While other strings like 'upstream_sfp_name' might be checked before
> access in certain code paths, failing to handle these allocations
> consistently can lead to incomplete data reporting or hidden bugs.
>
> Fix this by adding proper NULL checks for all kstrdup() calls in
> phy_prepare_data() and implement a centralized error handling path
> using goto labels to ensure all previously allocated resources are
> freed on failure.
>
> Fixes: 9dd2ad5e92b9 ("net: ethtool: phy: Convert the PHY_GET command to generic phy dump")
> Signed-off-by: Quan Sun <2022090917019@std.uestc.edu.cn>
Reviewed-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
Thanks,
Maxime
> ---
> Changes in v2:
> - Add Fixes: tag.
> - Expand the fix to cover all kstrdup() allocations in the function.
> - Use goto labels for a cleaner and more robust error handling path.
> ---
> net/ethtool/phy.c | 32 ++++++++++++++++++++++++++++++--
> 1 file changed, 30 insertions(+), 2 deletions(-)
>
> diff --git a/net/ethtool/phy.c b/net/ethtool/phy.c
> index d4e6887055ab1..f76d94d848d6d 100644
> --- a/net/ethtool/phy.c
> +++ b/net/ethtool/phy.c
> @@ -76,6 +76,7 @@ static int phy_prepare_data(const struct ethnl_req_info *req_info,
> struct nlattr **tb = info->attrs;
> struct phy_device_node *pdn;
> struct phy_device *phydev;
> + int ret;
>
> /* RTNL is held by the caller */
> phydev = ethnl_req_get_phydev(req_info, tb, ETHTOOL_A_PHY_HEADER,
> @@ -88,8 +89,17 @@ static int phy_prepare_data(const struct ethnl_req_info *req_info,
> return -EOPNOTSUPP;
>
> rep_data->phyindex = phydev->phyindex;
> +
> rep_data->name = kstrdup(dev_name(&phydev->mdio.dev), GFP_KERNEL);
> + if (!rep_data->name)
> + return -ENOMEM;
> +
> rep_data->drvname = kstrdup(phydev->drv->name, GFP_KERNEL);
> + if (!rep_data->drvname) {
> + ret = -ENOMEM;
> + goto err_free_name;
> + }
> +
> rep_data->upstream_type = pdn->upstream_type;
>
> if (pdn->upstream_type == PHY_UPSTREAM_PHY) {
> @@ -97,15 +107,33 @@ static int phy_prepare_data(const struct ethnl_req_info *req_info,
> rep_data->upstream_index = upstream->phyindex;
> }
>
> - if (pdn->parent_sfp_bus)
> + if (pdn->parent_sfp_bus) {
> rep_data->upstream_sfp_name = kstrdup(sfp_get_name(pdn->parent_sfp_bus),
> GFP_KERNEL);
> + if (!rep_data->upstream_sfp_name) {
> + ret = -ENOMEM;
> + goto err_free_drvname;
> + }
> + }
>
> - if (phydev->sfp_bus)
> + if (phydev->sfp_bus) {
> rep_data->downstream_sfp_name = kstrdup(sfp_get_name(phydev->sfp_bus),
> GFP_KERNEL);
> + if (!rep_data->downstream_sfp_name) {
> + ret = -ENOMEM;
> + goto err_free_upstream_sfp;
> + }
> + }
>
> return 0;
> +
> +err_free_upstream_sfp:
> + kfree(rep_data->upstream_sfp_name);
> +err_free_drvname:
> + kfree(rep_data->drvname);
> +err_free_name:
> + kfree(rep_data->name);
> + return ret;
> }
>
> static int phy_fill_reply(struct sk_buff *skb,
next prev parent reply other threads:[~2026-05-07 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 13:17 [PATCH net v2] net: ethtool: fix NULL pointer dereference in phy_reply_size Quan Sun
2026-05-07 15:39 ` Maxime Chevallier [this message]
2026-05-08 22:31 ` Jakub Kicinski
2026-05-08 22:40 ` patchwork-bot+netdevbpf
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=329ee928-2694-4348-a6f7-099618081dde@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=2022090917019@std.uestc.edu.cn \
--cc=andrew@lunn.ch \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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