All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
	luiz.dentz@gmail.com, kuni1840@gmail.com,
	linux-bluetooth@vger.kernel.org,
	syzbot+e4d73b165c3892852d22@syzkaller.appspotmail.com
Subject: Re: [PATCH] Bluetooth: Fix null-ptr-deref in l2cap_sock_resume_cb()
Date: Tue, 08 Jul 2025 21:00:06 +0000	[thread overview]
Message-ID: <175200840627.14772.9685536220181964734.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250707192832.3162227-1-kuniyu@google.com>

Hello:

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

On Mon,  7 Jul 2025 19:28:29 +0000 you wrote:
> syzbot reported null-ptr-deref in l2cap_sock_resume_cb(). [0]
> 
> l2cap_sock_resume_cb() has a similar problem that was fixed by commit
> 1bff51ea59a9 ("Bluetooth: fix use-after-free error in lock_sock_nested()").
> 
> Since both l2cap_sock_kill() and l2cap_sock_resume_cb() are executed
> under l2cap_sock_resume_cb(), we can avoid the issue simply by checking
> if chan->data is NULL.
> 
> [...]

Here is the summary with links:
  - Bluetooth: Fix null-ptr-deref in l2cap_sock_resume_cb()
    https://git.kernel.org/bluetooth/bluetooth-next/c/3092dfdfc57c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-07-08 20:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-07 19:28 [PATCH] Bluetooth: Fix null-ptr-deref in l2cap_sock_resume_cb() Kuniyuki Iwashima
2025-07-07 19:57 ` bluez.test.bot
2025-07-08 21: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=175200840627.14772.9685536220181964734.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=johan.hedberg@gmail.com \
    --cc=kuni1840@gmail.com \
    --cc=kuniyu@google.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=syzbot+e4d73b165c3892852d22@syzkaller.appspotmail.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.