From: patchwork-bot+netdevbpf@kernel.org
To: Duoming Zhou <duoming@zju.edu.cn>
Cc: linux-kernel@vger.kernel.org, isdn@linux-pingi.de,
kuba@kernel.org, andrii@kernel.org, gregkh@linuxfoundation.org,
axboe@kernel.dk, davem@davemloft.net, netdev@vger.kernel.org,
zou_wei@huawei.com
Subject: Re: [PATCH] mISDN: hfcpci: Fix use-after-free bug in hfcpci_softirq
Date: Sun, 09 Oct 2022 19:00:14 +0000 [thread overview]
Message-ID: <166534201455.6058.9588339706087338743.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221009063731.22733-1-duoming@zju.edu.cn>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Sun, 9 Oct 2022 14:37:31 +0800 you wrote:
> The function hfcpci_softirq() is a timer handler. If it
> is running, the timer_pending() will return 0 and the
> del_timer_sync() in HFC_cleanup() will not be executed.
> As a result, the use-after-free bug will happen. The
> process is shown below:
>
> (cleanup routine) | (timer handler)
> HFC_cleanup() | hfcpci_softirq()
> if (timer_pending(&hfc_tl)) |
> del_timer_sync() |
> ... | ...
> pci_unregister_driver(hc) |
> driver_unregister | driver_for_each_device
> bus_remove_driver | _hfcpci_softirq
> driver_detach | ...
> put_device(dev) //[1]FREE |
> | dev_get_drvdata(dev) //[2]USE
>
> [...]
Here is the summary with links:
- mISDN: hfcpci: Fix use-after-free bug in hfcpci_softirq
https://git.kernel.org/netdev/net/c/175302f6b79e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-10-09 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 6:37 [PATCH] mISDN: hfcpci: Fix use-after-free bug in hfcpci_softirq Duoming Zhou
2022-10-09 19:00 ` patchwork-bot+netdevbpf [this message]
2022-11-10 17:48 ` Greg KH
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=166534201455.6058.9588339706087338743.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=duoming@zju.edu.cn \
--cc=gregkh@linuxfoundation.org \
--cc=isdn@linux-pingi.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=zou_wei@huawei.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 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).