All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?SsOpcsOpbXkgSmVhbiA8SmVyZW15LkplYW5Ab3NzLmN5YmVyLmdvdXYuZnI+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: subash.a.kasiviswanathan@oss.qualcomm.com,
	sean.tranchetti@oss.qualcomm.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v2] net: qualcomm: rmnet: avoid stale VND access on TX drop
Date: Tue, 10 Nov 2026 02:55:24 +0000	[thread overview]
Message-ID: <179427932474.3612825.13986957054931266186.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261101232354.2047804-2-Jeremy.Jean@oss.cyber.gouv.fr>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Sun,  1 Nov 2026 23:23:54 +0000 you wrote:
> A struct rmnet_port stores a pointer to the most recently created
> RMNET VND in port->rmnet_dev, but userspace can delete that VND while
> the port still has another attached VND. When RMNET later sends a
> buffered TX skb, a failure in __skb_linearize() makes rmnet_send_skb()
> update the drop counter through that stale pointer, which causes a UAF.
> 
> The stale pointer can also be used by rmnet_unregister_bridge() when a
> real device leaves bridge mode. In that case it is passed to
> netdev_upper_dev_unlink(), which dereferences the freed VND and leaves
> the actual bridge adjacency behind.
> 
> [...]

Here is the summary with links:
  - [net,v2] net: qualcomm: rmnet: avoid stale VND access on TX drop
    https://git.kernel.org/netdev/net-next/c/4f89bcfa1e16

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-11-10  2:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-01 23:23 [PATCH net v2] net: qualcomm: rmnet: avoid stale VND access on TX drop Jérémy Jean
2026-11-01 23:29 ` netdev-bot+sinfo
2026-11-08 14:29   ` Simon Horman
2026-11-08  7:34 ` subash.a.kasiviswanathan
2026-11-10  2:55 ` patchwork-bot+netdevbpf [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=179427932474.3612825.13986957054931266186.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc==?utf-8?b?SsOpcsOpbXkgSmVhbiA8SmVyZW15LkplYW5Ab3NzLmN5YmVyLmdvdXYuZnI+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sean.tranchetti@oss.qualcomm.com \
    --cc=stable@vger.kernel.org \
    --cc=subash.a.kasiviswanathan@oss.qualcomm.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.