All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: SeungJu Cheon <suunj1331@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
	luiz.dentz@gmail.com, pmenzel@molgen.mpg.de,
	me@brighamcampbell.com, linux-kernel@vger.kernel.org,
	linux-kernel-mentees@lists.linux.dev, skhan@linuxfoundation.org,
	meatuni001@gmail.com
Subject: Re: [PATCH v3] Bluetooth: RFCOMM: validate skb length in MCC handlers
Date: Thu, 28 May 2026 14:20:06 +0000	[thread overview]
Message-ID: <177997800664.948024.5743539938103755383.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260525110443.139485-1-suunj1331@gmail.com>

Hello:

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

On Mon, 25 May 2026 20:04:43 +0900 you wrote:
> The RFCOMM MCC handlers cast skb->data to protocol-specific structs
> without validating skb->len first. A malicious remote device can send
> truncated MCC frames and trigger out-of-bounds reads in these handlers.
> 
> Fix this by using skb_pull_data() to validate and access the required
> data before dereferencing it.
> 
> [...]

Here is the summary with links:
  - [v3] Bluetooth: RFCOMM: validate skb length in MCC handlers
    https://git.kernel.org/bluetooth/bluetooth-next/c/a82ccb946ae5

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-28 14:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-25 11:04 [PATCH v3] Bluetooth: RFCOMM: validate skb length in MCC handlers SeungJu Cheon
2026-05-25 14:21 ` [v3] " bluez.test.bot
2026-05-28 14: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=177997800664.948024.5743539938103755383.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=me@brighamcampbell.com \
    --cc=meatuni001@gmail.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=skhan@linuxfoundation.org \
    --cc=suunj1331@gmail.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.