All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Jann Horn <jannh@google.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: bnep: Fix UAF read of dev->name
Date: Fri, 15 May 2026 15:50:07 +0000	[thread overview]
Message-ID: <177886020713.52984.6738499435725891558.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260512-bnep-add-uaf-v1-1-f62ff8f61d50@google.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Tue, 12 May 2026 22:15:39 +0200 you wrote:
> bnep_add_connection() needs to keep holding the bnep_session_sem while
> reading dev->name (just like bnep_get_connlist() does); otherwise the
> bnep_session() thread can concurrently free the net_device, which can for
> example be triggered by a concurrent bnep_del_connection().
> 
> (This UAF is fairly uninteresting from a security perspective;
> calling bnep_add_connection() requires passing a capable(CAP_NET_ADMIN)
> check. It also requires completely tearing down a netdev during a fairly
> tight race window.)
> 
> [...]

Here is the summary with links:
  - Bluetooth: bnep: Fix UAF read of dev->name
    https://git.kernel.org/bluetooth/bluetooth-next/c/ffeee619a13b

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-05-15 15:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12 20:15 [PATCH] Bluetooth: bnep: Fix UAF read of dev->name Jann Horn
2026-05-12 21:23 ` bluez.test.bot
2026-05-15 15:50 ` patchwork-bot+bluetooth [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=177886020713.52984.6738499435725891558.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=jannh@google.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --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 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.