From: patchwork-bot+bluetooth@kernel.org
To: Duoming Zhou <duoming@zju.edu.cn>
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, johan.hedberg@gmail.com,
marcel@holtmann.org
Subject: Re: [PATCH] Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout
Date: Fri, 03 May 2024 17:00:29 +0000 [thread overview]
Message-ID: <171475562973.29614.6591900788209831933.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240502125736.28034-1-duoming@zju.edu.cn>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 2 May 2024 20:57:36 +0800 you wrote:
> There is a race condition between l2cap_chan_timeout() and
> l2cap_chan_del(). When we use l2cap_chan_del() to delete the
> channel, the chan->conn will be set to null. But the conn could
> be dereferenced again in the mutex_lock() of l2cap_chan_timeout().
> As a result the null pointer dereference bug will happen. The
> KASAN report triggered by POC is shown below:
>
> [...]
Here is the summary with links:
- Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout
https://git.kernel.org/bluetooth/bluetooth-next/c/8192cea84c6c
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:[~2024-05-03 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 12:57 [PATCH] Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout Duoming Zhou
2024-05-02 13:33 ` bluez.test.bot
2024-05-03 17: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=171475562973.29614.6591900788209831933.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=duoming@zju.edu.cn \
--cc=johan.hedberg@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).