From: patchwork-bot+bluetooth@kernel.org
To: Helen Koike <koike@igalia.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-dev@igalia.com
Subject: Re: [PATCH] Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb
Date: Thu, 19 Mar 2026 18:10:06 +0000 [thread overview]
Message-ID: <177394380653.1743613.2960784486260115087.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260319115804.2160822-1-koike@igalia.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 19 Mar 2026 08:58:01 -0300 you wrote:
> Before using sk pointer, check if it is null.
>
> Fix the following:
>
> KASAN: null-ptr-deref in range [0x0000000000000260-0x0000000000000267]
> CPU: 0 UID: 0 PID: 5985 Comm: kworker/0:5 Not tainted 7.0.0-rc4-00029-ga989fde763f4 #1 PREEMPT(full)
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-9.fc43 06/10/2025
> Workqueue: events l2cap_info_timeout
> RIP: 0010:kasan_byte_accessible+0x12/0x30
> Code: 79 ff ff ff 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 40 d6 48 c1 ef 03 48 b8 00 00 00 00 00 fc ff df <0f> b6 04 07 3c 08 0f 92 c0 c3 cc cce
> veth0_macvtap: entered promiscuous mode
> RSP: 0018:ffffc90006e0f808 EFLAGS: 00010202
> RAX: dffffc0000000000 RBX: ffffffff89746018 RCX: 0000000080000001
> RDX: 0000000000000000 RSI: ffffffff89746018 RDI: 000000000000004c
> RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
> R10: dffffc0000000000 R11: ffffffff8aae3e70 R12: 0000000000000000
> R13: 0000000000000260 R14: 0000000000000260 R15: 0000000000000001
> FS: 0000000000000000(0000) GS:ffff8880983c2000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00005582615a5008 CR3: 000000007007e000 CR4: 0000000000752ef0
> PKRU: 55555554
> Call Trace:
> <TASK>
> __kasan_check_byte+0x12/0x40
> lock_acquire+0x79/0x2e0
> lock_sock_nested+0x48/0x100
> ? l2cap_sock_ready_cb+0x46/0x160
> l2cap_sock_ready_cb+0x46/0x160
> l2cap_conn_start+0x779/0xff0
> ? __pfx_l2cap_conn_start+0x10/0x10
> ? l2cap_info_timeout+0x60/0xa0
> ? __pfx___mutex_lock+0x10/0x10
> l2cap_info_timeout+0x68/0xa0
> ? process_scheduled_works+0xa8d/0x18c0
> process_scheduled_works+0xb6e/0x18c0
> ? __pfx_process_scheduled_works+0x10/0x10
> ? assign_work+0x3d5/0x5e0
> worker_thread+0xa53/0xfc0
> kthread+0x388/0x470
> ? __pfx_worker_thread+0x10/0x10
> ? __pfx_kthread+0x10/0x10
> ret_from_fork+0x51e/0xb90
> ? __pfx_ret_from_fork+0x10/0x10
> veth1_macvtap: entered promiscuous mode
> ? __switch_to+0xc7d/0x1450
> ? __pfx_kthread+0x10/0x10
> ret_from_fork_asm+0x1a/0x30
> </TASK>
> Modules linked in:
>
> [...]
Here is the summary with links:
- Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb
https://git.kernel.org/bluetooth/bluetooth-next/c/bc280a5ed9ef
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-19 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 11:58 [PATCH] Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb Helen Koike
2026-03-19 12:26 ` bluez.test.bot
2026-03-19 18:10 ` 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=177394380653.1743613.2960784486260115087.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=kernel-dev@igalia.com \
--cc=koike@igalia.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.