From: patchwork-bot+netdevbpf@kernel.org
To: Duoming Zhou <duoming@zju.edu.cn>
Cc: netdev@vger.kernel.org, krzysztof.kozlowski@linaro.org,
linux-kernel@vger.kernel.org, davem@davemloft.net,
gregkh@linuxfoundation.org, alexander.deucher@amd.com,
broonie@kernel.org, kuba@kernel.org
Subject: Re: [PATCH net] nfc: pn533: Fix use-after-free bugs caused by pn532_cmd_timeout
Date: Mon, 22 Aug 2022 14:00:15 +0000 [thread overview]
Message-ID: <166117681546.22523.17720942204050886000.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220818090621.106094-1-duoming@zju.edu.cn>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 18 Aug 2022 17:06:21 +0800 you wrote:
> When the pn532 uart device is detaching, the pn532_uart_remove()
> is called. But there are no functions in pn532_uart_remove() that
> could delete the cmd_timeout timer, which will cause use-after-free
> bugs. The process is shown below:
>
> (thread 1) | (thread 2)
> | pn532_uart_send_frame
> pn532_uart_remove | mod_timer(&pn532->cmd_timeout,...)
> ... | (wait a time)
> kfree(pn532) //FREE | pn532_cmd_timeout
> | pn532_uart_send_frame
> | pn532->... //USE
>
> [...]
Here is the summary with links:
- [net] nfc: pn533: Fix use-after-free bugs caused by pn532_cmd_timeout
https://git.kernel.org/netdev/net/c/f1e941dbf80a
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:[~2022-08-22 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 9:06 [PATCH net] nfc: pn533: Fix use-after-free bugs caused by pn532_cmd_timeout Duoming Zhou
2022-08-22 14:00 ` patchwork-bot+netdevbpf [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=166117681546.22523.17720942204050886000.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexander.deucher@amd.com \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=duoming@zju.edu.cn \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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 NNTP newsgroup(s).