All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Jiale Yao <yaojiale02@163.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, kees@kernel.org,
	kuba@kernel.org, hadess@hadess.net, suunj1331@gmail.com,
	pengpeng@iscas.ac.cn, tim.bird@sony.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: RFCOMM: validate skb length in rfcomm_recv_frame
Date: Fri, 24 Jul 2026 19:00:10 +0000	[thread overview]
Message-ID: <178491961039.3273549.4096598946894620170.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260722092616.1122797-1-yaojiale02@163.com>

Hello:

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

On Wed, 22 Jul 2026 17:26:14 +0800 you wrote:
> rfcomm_recv_frame() casts skb->data to struct rfcomm_hdr and dereferences
> hdr->addr and hdr->ctrl without validating skb->len first. A truncated
> frame with skb->len less than the minimum header size causes an
> out-of-bounds read of uninitialized memory. Additionally, a zero-length
> frame causes skb->len-- to underflow to UINT_MAX, making
> skb_tail_pointer() read far past the buffer.
> 
> [...]

Here is the summary with links:
  - Bluetooth: RFCOMM: validate skb length in rfcomm_recv_frame
    https://git.kernel.org/bluetooth/bluetooth-next/c/4c7de7083a9a

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-07-24 19:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22  9:26 [PATCH] Bluetooth: RFCOMM: validate skb length in rfcomm_recv_frame Jiale Yao
2026-07-22 10:02 ` bluez.test.bot
2026-07-24 19:00 ` 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=178491961039.3273549.4096598946894620170.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=hadess@hadess.net \
    --cc=kees@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=pengpeng@iscas.ac.cn \
    --cc=suunj1331@gmail.com \
    --cc=tim.bird@sony.com \
    --cc=yaojiale02@163.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.