From: Andrew Lunn <andrew@lunn.ch>
To: Simon Horman <horms@kernel.org>
Cc: Konrad Leszczynski <konrad.leszczynski@intel.com>,
davem@davemloft.net, andrew+netdev@lunn.ch, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, cezary.rojewski@intel.com,
sebastian.basierski@intel.com
Subject: Re: [PATCH net v4 1/2] net: stmmac: replace memcpy with ethtool_puts in ethtool
Date: Tue, 16 Sep 2025 19:12:22 +0200 [thread overview]
Message-ID: <8cc527bc-41cd-48ae-a40a-05c69b2c4ac3@lunn.ch> (raw)
In-Reply-To: <20250916164530.GM224143@horms.kernel.org>
On Tue, Sep 16, 2025 at 05:45:30PM +0100, Simon Horman wrote:
> On Tue, Sep 16, 2025 at 02:09:31PM +0200, Konrad Leszczynski wrote:
> > Fix kernel exception by replacing memcpy with ethtool_puts when used with
> > safety feature strings in ethtool logic.
> >
> > [ +0.000023] BUG: KASAN: global-out-of-bounds in stmmac_get_strings+0x17d/0x520 [stmmac]
> > [ +0.000115] Read of size 32 at addr ffffffffc0cfab20 by task ethtool/2571
> >
> > [ +0.000005] Call Trace:
> > [ +0.000004] <TASK>
> > [ +0.000003] dump_stack_lvl+0x6c/0x90
> > [ +0.000016] print_report+0xce/0x610
> > [ +0.000011] ? stmmac_get_strings+0x17d/0x520 [stmmac]
> > [ +0.000108] ? kasan_addr_to_slab+0xd/0xa0
> > [ +0.000008] ? stmmac_get_strings+0x17d/0x520 [stmmac]
> > [ +0.000101] kasan_report+0xd4/0x110
> > [ +0.000010] ? stmmac_get_strings+0x17d/0x520 [stmmac]
> > [ +0.000102] kasan_check_range+0x3a/0x1c0
> > [ +0.000010] __asan_memcpy+0x24/0x70
> > [ +0.000008] stmmac_get_strings+0x17d/0x520 [stmmac]
> >
> > Reviewed-by: Sebastian Basierski <sebastian.basierski@intel.com>
> > Reviewed-by: Cezary Rojewski <cezary.rojewski@intel.com>
> > Signed-off-by: Konrad Leszczynski <konrad.leszczynski@intel.com>
>
> As per my comment on v3 (sorry, I missed that you had already posted v4):
>
> I think it would be good to explain why using memcpy() is a problem here.
>
> I looked and it seems to me that one reason is that the strings may be
> too long.
I actually think the strings are too short. But i could be wrong.
In general, stmmac uses:
struct stmmac_stats {
char stat_string[ETH_GSTRING_LEN] __nonstring;
int sizeof_stat;
int stat_offset;
};
so the string is guaranteed to be long enough. However, these 'safety'
features make use of
struct dwmac5_error_desc {
bool valid;
const char *desc;
const char *detailed_desc;
};
where desc can be any length, ironically making
dwmac5_safety_feat_dump() unsafe. This is why i asked that this be
changed to be the same stmmac_stats, so [ETH_GSTRING_LEN]
__nonstring. But that seems to of fallen on deaf ears.
Andrew
next prev parent reply other threads:[~2025-09-16 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 12:09 [PATCH net v4 0/2] net: stmmac: misc fixes Konrad Leszczynski
2025-09-16 12:09 ` [PATCH net v4 1/2] net: stmmac: replace memcpy with ethtool_puts in ethtool Konrad Leszczynski
2025-09-16 16:45 ` Simon Horman
2025-09-16 17:12 ` Andrew Lunn [this message]
2025-09-16 23:25 ` Jakub Kicinski
2025-09-17 15:54 ` Tony Nguyen
2025-09-16 12:09 ` [PATCH net v4 2/2] net: stmmac: check if interface is running before TC block setup Konrad Leszczynski
2025-09-16 23:25 ` Jakub Kicinski
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=8cc527bc-41cd-48ae-a40a-05c69b2c4ac3@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=cezary.rojewski@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=konrad.leszczynski@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sebastian.basierski@intel.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
all inboxes | Powered by JetHome®