From: Lukasz Luba <lukasz.luba@arm.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Malaya Kumar Rout <mrout@redhat.com>
Cc: malayarout91@gmail.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PM: EM: Fix NULL pointer dereference in em_create_pd()
Date: Wed, 21 Jan 2026 12:22:30 +0000 [thread overview]
Message-ID: <50460dd0-1ed3-4976-ad9d-d9111c0147b8@arm.com> (raw)
In-Reply-To: <CAJZ5v0iB2fqiab2Uj7Et_+qztx208cFKHuS7e_Y9ATmgr09jyw@mail.gmail.com>
On 1/15/26 20:30, Rafael J. Wysocki wrote:
> On Thu, Jan 15, 2026 at 11:37 AM Malaya Kumar Rout <mrout@redhat.com> wrote:
>>
>> The get_cpu_device() function can return NULL if the CPU device is
>> not registered. However, the code in em_create_pd() dereferences the
>> returned pointer without checking for NULL, which can lead to a kernel
>> panic during energy model initialization.
>>
>> Add a NULL check before dereferencing cpu_dev. If get_cpu_device()
>> returns NULL, return -ENODEV and properly clean up allocated resources
>> through the existing error path.
>>
>> This issue was found by code inspection. The same function is correctly
>> handled with NULL checking in em_cpu_get() at line 555-557.
>>
>> Fixes: 1bc138c62295 ("PM / EM: add support for other devices than CPUs in Energy Model")
>> Signed-off-by: Malaya Kumar Rout <mrout@redhat.com>
>> ---
>> kernel/power/energy_model.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/kernel/power/energy_model.c b/kernel/power/energy_model.c
>> index 11af9f64aa82..3971743d7e67 100644
>> --- a/kernel/power/energy_model.c
>> +++ b/kernel/power/energy_model.c
>> @@ -466,6 +466,10 @@ static int em_create_pd(struct device *dev, int nr_states,
>> if (_is_cpu_device(dev))
>> for_each_cpu(cpu, cpus) {
>> cpu_dev = get_cpu_device(cpu);
>> + if (!cpu_dev) {
>> + ret = -ENODEV;
>> + goto free_pd_table;
>
> No, you need to clear em_pd for the CPUs for which it has been set already.
>
> Maybe it would be better to do this check upfront for all CPUs in the
> mask. Lukasz?
>
Right, let me study this and come back with the recommendation...
prev parent reply other threads:[~2026-01-21 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 10:37 Malaya Kumar Rout
2026-01-15 20:30 ` Rafael J. Wysocki
2026-01-21 12:22 ` Lukasz Luba [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=50460dd0-1ed3-4976-ad9d-d9111c0147b8@arm.com \
--to=lukasz.luba@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=malayarout91@gmail.com \
--cc=mrout@redhat.com \
--cc=rafael@kernel.org \
/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®