From: Greg KH <gregkh@linuxfoundation.org>
To: Chaitanya Mishra <chaitanyamishra.ai@gmail.com>
Cc: rmfrfs@gmail.com, johan@kernel.org, elder@kernel.org,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: greybus: lights: avoid NULL deref
Date: Thu, 8 Jan 2026 11:46:26 +0100 [thread overview]
Message-ID: <2026010814-displease-jawed-688e@gregkh> (raw)
In-Reply-To: <20260108103700.15384-1-chaitanyamishra.ai@gmail.com>
On Thu, Jan 08, 2026 at 04:07:00PM +0530, Chaitanya Mishra wrote:
> gb_lights_light_config() stores channel_count before allocating the
> channels array. If kcalloc() fails, gb_lights_release() iterates the
> non-zero count and dereferences light->channels, which is NULL.
>
> Allocate channels first and only then publish channels_count so the
> cleanup path can't walk a NULL pointer.
How was this issue found? How was the fix generated? How was it
tested?
>
> Fixes: 2870b52bae4c ("greybus: lights: add lights implementation")
> Signed-off-by: Chaitanya Mishra <chaitanyamishra.ai@gmail.com>
> ---
> drivers/staging/greybus/light.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/greybus/light.c b/drivers/staging/greybus/light.c
> index e509fdc715db..4c9ad9ea8827 100644
> --- a/drivers/staging/greybus/light.c
> +++ b/drivers/staging/greybus/light.c
> @@ -1008,14 +1008,14 @@ static int gb_lights_light_config(struct gb_lights *glights, u8 id)
> if (!strlen(conf.name))
> return -EINVAL;
>
> - light->channels_count = conf.channel_count;
> light->name = kstrndup(conf.name, NAMES_MAX, GFP_KERNEL);
> if (!light->name)
> return -ENOMEM;
> - light->channels = kcalloc(light->channels_count,
> + light->channels = kcalloc(conf.channel_count,
> sizeof(struct gb_channel), GFP_KERNEL);
> if (!light->channels)
> return -ENOMEM;
> + light->channels_count = conf.channel_count;
This is "tricky", perhaps add a comment here as to why you are only
assigning this now and not before?
thanks,
greg k-h
next prev parent reply other threads:[~2026-01-08 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 10:37 [PATCH] staging: greybus: lights: avoid NULL deref Chaitanya Mishra
2026-01-08 10:46 ` Greg KH [this message]
2026-01-08 10:49 ` [PATCH v2] " Chaitanya Mishra
2026-01-08 11:01 ` Greg KH
2026-01-08 11:03 ` Chaitanya Mishra
2026-01-08 11:17 ` Greg KH
2026-01-08 11:05 ` Rui Miguel Silva
2026-01-08 11:07 ` [PATCH v3] " Chaitanya Mishra
2026-01-08 11:09 ` Chaitanya Mishra
2026-01-08 11:18 ` Greg KH
2026-01-08 11:23 ` Chaitanya Mishra
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=2026010814-displease-jawed-688e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=chaitanyamishra.ai@gmail.com \
--cc=elder@kernel.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=rmfrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox