All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Binbin Zhou <zhoubinbin@loongson.cn>,
	Gustavo A. R. Silva <gustavoars@kernel.org>,
	Huacai Chen <chenhuacai@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Yinbo Zhu <zhuyinbo@loongson.cn>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	Gustavo A. R. Silva <gustavoars@kernel.org>,
	linux-hardening@vger.kernel.org
Subject: Re: [PATCH] clk: clk-loongson2: Fix potential buffer overflow in flexible-array member access
Date: Thu, 14 Nov 2024 17:35:41 -0800	[thread overview]
Message-ID: <ed2e1be4be4716b2c436a163ae40ef07.sboyd@kernel.org> (raw)
In-Reply-To: <ZzaN5MpmMr0hwHw9@kspp>

Quoting Gustavo A. R. Silva (2024-11-14 15:55:16)
> Flexible-array member `hws` in `struct clk_hw_onecell_data` is annotated
> with the `counted_by()` attribute. This means that when memory is
> allocated for this array, the _counter_, which in this case is member
> `num` in the flexible structure, should be set to the maximum number of
> elements the flexible array can contain, or fewer.
> 
> In this case, the total number of elements for the flexible array is
> determined by variable `clks_num` when allocating heap space via
> `devm_kzalloc()`, as shown below:
> 
> 289         struct loongson2_clk_provider *clp;
>         ...
> 296         for (p = data; p->name; p++)
> 297                 clks_num++;
> 298
> 299         clp = devm_kzalloc(dev, struct_size(clp, clk_data.hws, clks_num),
> 300                            GFP_KERNEL);
> 
> So, `clp->clk_data.num` should be set to `clks_num` or less, and not
> exceed `clks_num`, as is currently the case. Otherwise, if data is
> written into `clp->clk_data.hws[clks_num]`, the instrumentation
> provided by the compiler won't detect the overflow, leading to a
> memory corruption bug at runtime.
> 
> Fix this issue by setting `clp->clk_data.num` to `clks_num`.
> 
> Fixes: 9796ec0bd04b ("clk: clk-loongson2: Refactor driver for adding new platforms")
> Cc: stable@vger.kernel.org
> Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
> ---

Applied to clk-next

      reply	other threads:[~2024-11-15  1:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14 23:55 [PATCH] clk: clk-loongson2: Fix potential buffer overflow in flexible-array member access Gustavo A. R. Silva
2024-11-15  1:35 ` Stephen Boyd [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=ed2e1be4be4716b2c436a163ae40ef07.sboyd@kernel.org \
    --to=sboyd@kernel.org \
    --cc=chenhuacai@kernel.org \
    --cc=gustavoars@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=zhoubinbin@loongson.cn \
    --cc=zhuyinbo@loongson.cn \
    /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.