From: patchwork-bot+bluetooth@kernel.org
To: Keenan Dong <keenanat2000@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: MGMT: validate LTK enc_size on load
Date: Mon, 30 Mar 2026 20:20:05 +0000 [thread overview]
Message-ID: <177490200553.1507090.8760884418467627395.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260328084648.51158-1-keenanat2000@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sat, 28 Mar 2026 16:46:47 +0800 you wrote:
> Load Long Term Keys stores the user-provided enc_size and later uses
> it to size fixed-size stack operations when replying to LE LTK
> requests. An enc_size larger than the 16-byte key buffer can therefore
> overflow the reply stack buffer.
>
> Reject oversized enc_size values while validating the management LTK
> record so invalid keys never reach the stored key state.
>
> [...]
Here is the summary with links:
- Bluetooth: MGMT: validate LTK enc_size on load
https://git.kernel.org/bluetooth/bluetooth-next/c/2ba40afb67d1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-03-30 20:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 8:46 [PATCH] Bluetooth: MGMT: validate LTK enc_size on load Keenan Dong
2026-03-28 8:46 ` [PATCH] Bluetooth: MGMT: require exact mesh send payload length Keenan Dong
2026-03-28 9:53 ` bluez.test.bot
2026-03-30 20:06 ` [PATCH] " Luiz Augusto von Dentz
2026-04-01 14:52 ` Keenan Dong
2026-04-01 14:25 ` [PATCH v2] Bluetooth: MGMT: validate mesh send advertising " Keenan Dong
2026-04-01 15:10 ` [v2] " bluez.test.bot
2026-04-01 18:30 ` [PATCH v2] " patchwork-bot+bluetooth
2026-03-28 9:52 ` Bluetooth: MGMT: validate LTK enc_size on load bluez.test.bot
2026-03-30 20: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=177490200553.1507090.8760884418467627395.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=keenanat2000@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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.