From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Duoming Zhou <duoming@zju.edu.cn>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, kuba@kernel.org,
edumazet@google.com, davem@davemloft.net, andrew+netdev@lunn.ch,
jonathan.lemon@gmail.com, richardcochran@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog
Date: Thu, 28 Aug 2025 12:11:36 +0100 [thread overview]
Message-ID: <25ff983c-8479-4c2e-9afc-2a3befedabb0@linux.dev> (raw)
In-Reply-To: <20250828082949.28189-1-duoming@zju.edu.cn>
On 28/08/2025 09:29, Duoming Zhou wrote:
> The ptp_ocp_detach() only shuts down the watchdog timer if it is
> pending. However, if the timer handler is already running, the
> timer_delete_sync() is not called. This leads to race conditions
> where the devlink that contains the ptp_ocp is deallocated while
> the timer handler is still accessing it, resulting in use-after-free
> bugs. The following details one of the race scenarios.
>
> (thread 1) | (thread 2)
> ptp_ocp_remove() |
> ptp_ocp_detach() | ptp_ocp_watchdog()
> if (timer_pending(&bp->watchdog))| bp = timer_container_of()
> timer_delete_sync() |
> |
> devlink_free(devlink) //free |
> | bp-> //use
>
> Resolve this by unconditionally calling timer_delete_sync() to ensure
> the timer is reliably deactivated, preventing any access after free.
>
> Fixes: 773bda964921 ("ptp: ocp: Expose various resources on the timecard.")
> Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
Reviewed-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
> ---
> drivers/ptp/ptp_ocp.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/ptp/ptp_ocp.c b/drivers/ptp/ptp_ocp.c
> index d39073dc4072..4e1286ce05c9 100644
> --- a/drivers/ptp/ptp_ocp.c
> +++ b/drivers/ptp/ptp_ocp.c
> @@ -4557,8 +4557,7 @@ ptp_ocp_detach(struct ptp_ocp *bp)
> ptp_ocp_debugfs_remove_device(bp);
> ptp_ocp_detach_sysfs(bp);
> ptp_ocp_attr_group_del(bp);
> - if (timer_pending(&bp->watchdog))
> - timer_delete_sync(&bp->watchdog);
> + timer_delete_sync(&bp->watchdog);
> if (bp->ts0)
> ptp_ocp_unregister_ext(bp->ts0);
> if (bp->ts1)
next prev parent reply other threads:[~2025-08-28 11:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 8:29 [PATCH net] ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog Duoming Zhou
2025-08-28 11:11 ` Vadim Fedorenko [this message]
2025-08-30 2:20 ` patchwork-bot+netdevbpf
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=25ff983c-8479-4c2e-9afc-2a3befedabb0@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=duoming@zju.edu.cn \
--cc=edumazet@google.com \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.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.