mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shree Ramamoorthy <s-ramamoorthy@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: <aaro.koskinen@iki.fi>, <andreas@kemnade.info>,
	<khilman@baylibre.com>, <rogerq@kernel.org>, <tony@atomide.com>,
	<lee@kernel.org>, <d-gole@ti.com>, <robertcnelson@gmail.com>,
	<jkridner@gmail.com>, <linux-omap@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <m-leonard@ti.com>,
	<praneeth@ti.com>, <afd@ti.com>, <broonie@kernel.org>
Subject: Re: [PATCH v2] regulator: tps65219: Fix devm_kmalloc size allocation
Date: Fri, 27 Jun 2025 14:45:58 -0500	[thread overview]
Message-ID: <fcd02d29-3d39-49fe-8ec5-97f2db024f1f@ti.com> (raw)
In-Reply-To: <20250627193150.nxer4zuowaejzp4v@unarmored>

+Mark. Sorry, missed cc'ing you on this series!

On 6/27/2025 2:31 PM, Nishanth Menon wrote:
> On 10:45-20250620, Shree Ramamoorthy wrote:
>> In probe(), two arrays of structs are allocated with the devm_kmalloc()
>> function, but the memory size of the allocations were given as the arrays'
>> length (pmic->common_irq_size for the first call and pmic->dev_irq_size for
>> the second devm_kmalloc call). The memory size should have been the total
>> memory needed.
>>
>> This led to a heap overflow when the struct array was used. The issue was
>> first discovered with the PocketBeagle2 and BeaglePlay. The common and
>> device-specific structs are now allocated one at a time within the loop.
>>
>> Fixes: 38c9f98db20a ("regulator: tps65219: Add support for TPS65215 Regulator IRQs")
>> Reported-by: Dhruva Gole <d-gole@ti.com>
>> Closes: https://lore.kernel.org/all/20250619153526.297398-1-d-gole@ti.com/
>> Tested-by: Robert Nelson <robertcnelson@gmail.com>
>> Acked-by: Andrew Davis <afd@ti.com>
>> Signed-off-by: Shree Ramamoorthy <s-ramamoorthy@ti.com>
>> ---
>> v2: Update commit message explanation & tags.
>> ---
> Kasan also reports the same on latest next :(
> https://gist.github.com/nmenon/a0a020e8417c198d2f366fa00b900e12
>
> Could this be routed to master please?
>
> Reviewed-by: Nishanth Menon <nm@ti.com>
>
>>  drivers/regulator/tps65219-regulator.c | 28 +++++++++++++-------------
>>  1 file changed, 14 insertions(+), 14 deletions(-)
>>
>> diff --git a/drivers/regulator/tps65219-regulator.c b/drivers/regulator/tps65219-regulator.c
>> index b16b300d7f45..5e67fdc88f49 100644
>> --- a/drivers/regulator/tps65219-regulator.c
>> +++ b/drivers/regulator/tps65219-regulator.c
>> @@ -436,46 +436,46 @@ static int tps65219_regulator_probe(struct platform_device *pdev)
>>  					     pmic->rdesc[i].name);
>>  	}
>>  
>> -	irq_data = devm_kmalloc(tps->dev, pmic->common_irq_size, GFP_KERNEL);
>> -	if (!irq_data)
>> -		return -ENOMEM;
>> -
>>  	for (i = 0; i < pmic->common_irq_size; ++i) {
>>  		irq_type = &pmic->common_irq_types[i];
>>  		irq = platform_get_irq_byname(pdev, irq_type->irq_name);
>>  		if (irq < 0)
>>  			return -EINVAL;
>>  
>> -		irq_data[i].dev = tps->dev;
>> -		irq_data[i].type = irq_type;
>> +		irq_data = devm_kmalloc(tps->dev, sizeof(*irq_data), GFP_KERNEL);
>> +		if (!irq_data)
>> +			return -ENOMEM;
>> +
>> +		irq_data->dev = tps->dev;
>> +		irq_data->type = irq_type;
>>  		error = devm_request_threaded_irq(tps->dev, irq, NULL,
>>  						  tps65219_regulator_irq_handler,
>>  						  IRQF_ONESHOT,
>>  						  irq_type->irq_name,
>> -						  &irq_data[i]);
>> +						  irq_data);
>>  		if (error)
>>  			return dev_err_probe(tps->dev, PTR_ERR(rdev),
>>  					     "Failed to request %s IRQ %d: %d\n",
>>  					     irq_type->irq_name, irq, error);
>>  	}
>>  
>> -	irq_data = devm_kmalloc(tps->dev, pmic->dev_irq_size, GFP_KERNEL);
>> -	if (!irq_data)
>> -		return -ENOMEM;
>> -
>>  	for (i = 0; i < pmic->dev_irq_size; ++i) {
>>  		irq_type = &pmic->irq_types[i];
>>  		irq = platform_get_irq_byname(pdev, irq_type->irq_name);
>>  		if (irq < 0)
>>  			return -EINVAL;
>>  
>> -		irq_data[i].dev = tps->dev;
>> -		irq_data[i].type = irq_type;
>> +		irq_data = devm_kmalloc(tps->dev, sizeof(*irq_data), GFP_KERNEL);
>> +		if (!irq_data)
>> +			return -ENOMEM;
>> +
>> +		irq_data->dev = tps->dev;
>> +		irq_data->type = irq_type;
>>  		error = devm_request_threaded_irq(tps->dev, irq, NULL,
>>  						  tps65219_regulator_irq_handler,
>>  						  IRQF_ONESHOT,
>>  						  irq_type->irq_name,
>> -						  &irq_data[i]);
>> +						  irq_data);
>>  		if (error)
>>  			return dev_err_probe(tps->dev, PTR_ERR(rdev),
>>  					     "Failed to request %s IRQ %d: %d\n",
>>
>> base-commit: 75f5f23f8787c5e184fcb2fbcd02d8e9317dc5e7
>> -- 
>> 2.43.0
>>
>>

  reply	other threads:[~2025-06-27 19:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20 15:45 Shree Ramamoorthy
2025-06-27 19:31 ` Nishanth Menon
2025-06-27 19:45   ` Shree Ramamoorthy [this message]
2025-06-30 11:40 ` Mark Brown

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=fcd02d29-3d39-49fe-8ec5-97f2db024f1f@ti.com \
    --to=s-ramamoorthy@ti.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=afd@ti.com \
    --cc=andreas@kemnade.info \
    --cc=broonie@kernel.org \
    --cc=d-gole@ti.com \
    --cc=jkridner@gmail.com \
    --cc=khilman@baylibre.com \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=m-leonard@ti.com \
    --cc=nm@ti.com \
    --cc=praneeth@ti.com \
    --cc=robertcnelson@gmail.com \
    --cc=rogerq@kernel.org \
    --cc=tony@atomide.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

all inboxes | Powered by JetHome®