From: patchwork-bot+bluetooth@kernel.org
To: K@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
Kiran <kiran.k@intel.com>
Cc: linux-bluetooth@vger.kernel.org, ravishankar.srivatsa@intel.com,
chethan.tumkur.narayan@intel.com,
chandrashekar.devegowda@intel.com
Subject: Re: [PATCH v1] Bluetooth: btintel_pcie: cap device debug regions at 1 MB
Date: Tue, 08 Sep 2026 16:30:29 +0000 [thread overview]
Message-ID: <178888502963.3627954.4649873667262966331.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260908133421.163043-1-kiran.k@intel.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 8 Sep 2026 19:04:21 +0530 you wrote:
> Validate device-supplied debug-region boundaries during mailbox TLV
> parsing and convert start/end values to a validated region size. Cap
> debug-region sizes to 1 MB to prevent out-of-bounds reads if firmware
> reports oversized memory ranges. Skip invalid or oversized regions
> prior to coredump capture.
>
> This issue was reported by Claude Mythos.
>
> [...]
Here is the summary with links:
- [v1] Bluetooth: btintel_pcie: cap device debug regions at 1 MB
https://git.kernel.org/bluetooth/bluetooth-next/c/ea6d8993c910
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-09-08 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 13:34 [PATCH v1] Bluetooth: btintel_pcie: cap device debug regions at 1 MB Kiran K
2026-09-08 15:56 ` [v1] " bluez.test.bot
2026-09-08 16:30 ` 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=178888502963.3627954.4649873667262966331.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=K@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=chandrashekar.devegowda@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ravishankar.srivatsa@intel.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.