From: Kohei Enju <kohei@enjuk.jp>
To: Simon Horman <horms@kernel.org>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Faizal Rahim <faizal.abdul.rahim@linux.intel.com>,
kohei.enju@gmail.com, stable@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH iwl-net v2] igc: fix potential skb leak in igc_fpe_xmit_smd_frame()
Date: Sat, 18 Apr 2026 01:20:44 +0900 [thread overview]
Message-ID: <aeJdUhe7_x1ZKFzX@x1> (raw)
In-Reply-To: <20260417115122.GA31784@horms.kernel.org>
On 04/17 12:51, Simon Horman wrote:
> On Wed, Apr 15, 2026 at 02:52:18AM +0000, Kohei Enju wrote:
> > When igc_fpe_init_tx_descriptor() fails, no one takes care of an
> > allocated skb, leaking it. [1]
> > Use dev_kfree_skb_any() on failure.
> >
> > Tested on an I226 adapter with the following command, while injecting
> > faults in igc_fpe_init_tx_descriptor() to trigger the error path.
> > # ethtool --set-mm $DEV verify-enabled on tx-enabled on pmac-enabled on
> >
> > [1]
> > unreferenced object 0xffff888113c6cdc0 (size 224):
> > ...
> > backtrace (crc be3d3fda):
> > kmem_cache_alloc_node_noprof+0x3b1/0x410
> > __alloc_skb+0xde/0x830
> > igc_fpe_xmit_smd_frame.isra.0+0xad/0x1b0
> > igc_fpe_send_mpacket+0x37/0x90
> > ethtool_mmsv_verify_timer+0x15e/0x300
> >
> > Cc: stable@vger.kernel.org
> > Fixes: 5422570c0010 ("igc: add support for frame preemption verification")
> > Signed-off-by: Kohei Enju <kohei@enjuk.jp>
> > ---
> > Changes:
> > v2:
> > - change to idiomatic style with goto (Simon)
> > - add Cc to stable (Alex)
> > - add reprodunction steps (Alex)
> > v1: https://lore.kernel.org/all/20260329145122.126040-1-kohei@enjuk.jp/
>
> Thanks for the update.
>
> Reviewed-by: Simon Horman <horms@kernel.org>
>
> Sashiko has comments about a potential existing bug in the same code path.
> I'd appreciate it if, as a follow-up, you could look over that.
Thanks for the heads-up. I'll look into it.
>
> Thanks!
prev parent reply other threads:[~2026-04-17 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 2:52 [PATCH iwl-net v2] igc: fix potential skb leak in igc_fpe_xmit_smd_frame() Kohei Enju
2026-04-17 11:51 ` Simon Horman
2026-04-17 16:20 ` Kohei Enju [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=aeJdUhe7_x1ZKFzX@x1 \
--to=kohei@enjuk.jp \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=faizal.abdul.rahim@linux.intel.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kohei.enju@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox