From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Sagi Maimon <maimon.sagi@gmail.com>,
jonathan.lemon@gmail.com, richardcochran@gmail.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v1] ptp: ocp: fix NULL deref in _signal_summary_show
Date: Mon, 14 Apr 2025 10:37:26 +0100 [thread overview]
Message-ID: <b6aea926-ebb6-48fe-a1be-6f428a648eae@linux.dev> (raw)
In-Reply-To: <20250414085412.117120-1-maimon.sagi@gmail.com>
On 14/04/2025 09:54, Sagi Maimon wrote:
> Sysfs signal show operations can invoke _signal_summary_show before
> signal_out array elements are initialized, causing a NULL pointer
> dereference. Add NULL checks for signal_out elements to prevent kernel
> crashes.
>
> Fixes: b325af3cfab9 ("ptp: ocp: Add signal generators and update sysfs nodes")
> Signed-off-by: Sagi Maimon <maimon.sagi@gmail.com>
> ---
> drivers/ptp/ptp_ocp.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/ptp/ptp_ocp.c b/drivers/ptp/ptp_ocp.c
> index 7945c6be1f7c..4c7893539cec 100644
> --- a/drivers/ptp/ptp_ocp.c
> +++ b/drivers/ptp/ptp_ocp.c
> @@ -3963,6 +3963,9 @@ _signal_summary_show(struct seq_file *s, struct ptp_ocp *bp, int nr)
> bool on;
> u32 val;
>
> + if (!bp->signal_out[nr])
> + return;
> +
> on = signal->running;
> sprintf(label, "GEN%d", nr + 1);
> seq_printf(s, "%7s: %s, period:%llu duty:%d%% phase:%llu pol:%d",
That's not correct, the dereference of bp->signal_out[nr] happens before
the check. But I just wonder how can that even happen?
I believe the proper fix is to move ptp_ocp_attr_group_add() closer to
the end of ptp_ocp_adva_board_init() like it's done for other boards.
--
pw-bot: cr
next prev parent reply other threads:[~2025-04-14 9:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 8:54 [PATCH v1] ptp: ocp: fix NULL deref in _signal_summary_show Sagi Maimon
2025-04-14 9:37 ` Vadim Fedorenko [this message]
2025-04-14 10:56 ` Sagi Maimon
2025-04-14 11:09 ` Vadim Fedorenko
2025-04-14 11:38 ` Sagi Maimon
2025-04-14 13:01 ` Vadim Fedorenko
2025-04-14 13:43 ` Sagi Maimon
2025-04-14 13:54 ` Vadim Fedorenko
2025-04-16 6:33 ` Sagi Maimon
2025-04-16 10:35 ` Vadim Fedorenko
2025-04-16 13:59 ` Sagi Maimon
2025-04-16 14:45 ` Vadim Fedorenko
2025-04-29 8:42 ` Sagi Maimon
2025-04-30 9:52 ` Vadim Fedorenko
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=b6aea926-ebb6-48fe-a1be-6f428a648eae@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maimon.sagi@gmail.com \
--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.