mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Zhao Li <enderaoelyther@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	johan.hedberg@intel.com, security@kernel.org,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Bluetooth: L2CAP: Match LE responses to outstanding requests
Date: Wed, 04 Nov 2026 22:20:23 +0000	[thread overview]
Message-ID: <179383082342.3253812.9942140641407431585.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261102124735.23199-1-enderaoelyther@gmail.com>

Hello:

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

On Mon,  2 Nov 2026 20:47:33 +0800 you wrote:
> An LE peer that can reach a local L2CAP listener can use unsolicited
> responses or Command Rejects to bypass deferred setup, remove an
> established channel, or leak an unaccepted socket and channel.
> Authentication requirements depend on the listener's security setting;
> whether a default configuration exposes such a listener has not been
> checked.
> 
> [...]

Here is the summary with links:
  - [1/2] Bluetooth: L2CAP: Only accept LE responses to outstanding requests
    https://git.kernel.org/bluetooth/bluetooth-next/c/f50b32aa233d
  - [2/2] Bluetooth: L2CAP: Clear request identifiers on incoming LE connections
    https://git.kernel.org/bluetooth/bluetooth-next/c/15a80cc8263a

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-04 22:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-02 12:47 Zhao Li
2026-11-02 12:47 ` [PATCH 1/2] Bluetooth: L2CAP: Only accept " Zhao Li
2026-11-02 12:47 ` [PATCH 2/2] Bluetooth: L2CAP: Clear request identifiers on incoming LE connections Zhao Li
2026-11-02 16:54   ` Greg KH
2026-11-04 22:20 ` 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=179383082342.3253812.9942140641407431585.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=enderaoelyther@gmail.com \
    --cc=johan.hedberg@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=security@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
all inboxes | Powered by JetHome®