From: Simon Horman <horms@kernel.org>
To: David Carlier <devnexen@gmail.com>
Cc: MD Danish Anwar <danishanwar@ti.com>,
Roger Quadros <rogerq@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH net] net: ti: icssg-prueth: fix use-after-free of CPPI descriptor in RX path
Date: Fri, 20 Mar 2026 17:27:20 +0000 [thread overview]
Message-ID: <20260320172720.GE74886@horms.kernel.org> (raw)
In-Reply-To: <20260319181236.14526-1-devnexen@gmail.com>
On Thu, Mar 19, 2026 at 06:12:36PM +0000, David Carlier wrote:
> cppi5_hdesc_get_psdata() returns a pointer into the CPPI descriptor.
> In both emac_rx_packet() and emac_rx_packet_zc(), the descriptor is
> freed via k3_cppi_desc_pool_free() before the psdata pointer is used
> by emac_rx_timestamp(), which dereferences psdata[0] and psdata[1].
> This constitutes a use-after-free on every received packet that goes
> through the timestamp path.
>
> Defer the descriptor free until after all accesses through the psdata
> pointer are complete. For emac_rx_packet(), this means freeing in each
> early-exit path and after emac_rx_timestamp() in the success path. For
> emac_rx_packet_zc(), move the free to the end of the loop body after
> emac_dispatch_skb_zc() (which calls emac_rx_timestamp()) has returned.
>
> Fixes: 46eeb90f03e0 ("net: ti: icssg-prueth: Use page_pool API for RX buffer allocation")
> Signed-off-by: David Carlier <devnexen@gmail.com>
> ---
> drivers/net/ethernet/ti/icssg/icssg_common.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/ethernet/ti/icssg/icssg_common.c b/drivers/net/ethernet/ti/icssg/icssg_common.c
...
> @@ -1057,7 +1057,6 @@ static int emac_rx_packet(struct prueth_emac *emac, u32 flow_id, u32 *xdp_state)
> /* firmware adds 4 CRC bytes, strip them */
> pkt_len -= 4;
> cppi5_desc_get_tags_ids(&desc_rx->hdr, &port_id, NULL);
> - k3_cppi_desc_pool_free(rx_chn->desc_pool, desc_rx);
>
> /* if allocation fails we drop the packet but push the
> * descriptor back to the ring with old page to prevent a stall
> @@ -1066,6 +1065,7 @@ static int emac_rx_packet(struct prueth_emac *emac, u32 flow_id, u32 *xdp_state)
> if (unlikely(!new_page)) {
> new_page = page;
> ndev->stats.rx_dropped++;
> + k3_cppi_desc_pool_free(rx_chn->desc_pool, desc_rx);
> goto requeue;
Hi David,
I am sorry for not noticing this earlier.
It seems to me that with this patch k3_cppi_desc_pool_free()
is always called before the requeue label is reached.
Would it make sense to move the call to k3_cppi_desc_pool_free()
into the requeue label? Or does it need to be called earlier
than that in the non-goto case?
> }
>
...
next prev parent reply other threads:[~2026-03-20 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 18:12 [PATCH net] net: ti: icssg-prueth: fix use-after-free of CPPI descriptor in RX path David Carlier
2026-03-20 17:27 ` Simon Horman [this message]
2026-03-20 17:44 ` [PATCH] " David Carlier
2026-03-21 10:31 ` Simon Horman
2026-03-24 11:30 ` 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=20260320172720.GE74886@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=devnexen@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rogerq@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