From: Breno Leitao <leitao@debian.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
joe@dama.to
Subject: Re: [PATCH net-next] netdevsim: fix UaF when counting Tx stats
Date: Fri, 20 Jun 2025 11:24:46 -0700 [thread overview]
Message-ID: <aFWnbtAtl1kA1zIo@gmail.com> (raw)
In-Reply-To: <20250620174007.2188470-1-kuba@kernel.org>
On Fri, Jun 20, 2025 at 10:40:07AM -0700, Jakub Kicinski wrote:
> skb may be freed as soon as we put it on the rx queue.
> Use the len variable like the code did prior to the conversion.
>
> Fixes: f9e2511d80c2 ("netdevsim: migrate to dstats stats collection")
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Reviewed-by: Breno Leitao <leitao@debian.org>
next prev parent reply other threads:[~2025-06-20 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 17:40 [PATCH net-next] netdevsim: fix UaF when counting Tx stats Jakub Kicinski
2025-06-20 17:53 ` David Miller
2025-06-20 18:24 ` Breno Leitao [this message]
2025-06-22 18:00 ` 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=aFWnbtAtl1kA1zIo@gmail.com \
--to=leitao@debian.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=joe@dama.to \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.