From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: <stable@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Henry Martin <bsdhenrymartin@gmail.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
<lvc-project@linuxtesting.org>
Subject: Re: [PATCH 5.10.y] cpufreq: scmi: Fix null-ptr-deref in scmi_cpufreq_get_rate()
Date: Tue, 16 Sep 2025 22:04:52 +0300 [thread overview]
Message-ID: <ed43a751-3b02-46db-9fe1-da6c9f79fd80@omp.ru> (raw)
In-Reply-To: <b6ebf19c-8328-44de-a695-157061a9d8a8@omp.ru>
On 9/12/25 11:35 PM, Sergey Shtylyov wrote:
> From: Henry Martin <bsdhenrymartin@gmail.com>
>
> [ Upstream commit 484d3f15cc6cbaa52541d6259778e715b2c83c54 ]
>
> cpufreq_cpu_get_raw() can return NULL when the target CPU is not present
> in the policy->cpus mask. scmi_cpufreq_get_rate() does not check for
> this case, which results in a NULL pointer dereference.
>
> Add NULL check after cpufreq_cpu_get_raw() to prevent this issue.
>
> [Sergey: resolved reject (reordering the local variables).]
>
> Fixes: 99d6bdf33877 ("cpufreq: add support for CPU DVFS based on SCMI message protocol")
> Signed-off-by: Henry Martin <bsdhenrymartin@gmail.com>
> Acked-by: Sudeep Holla <sudeep.holla@arm.com>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> Signed-off-by: Sergey Shtylyov <s.shtylyov@omp.ru>
Probably should have noted that this patch fixes CVE-2025-37830:
https://marc.info/?l=linux-cve-announce&m=174668615621702
(Sorry, lore doesn't work for me anymre...]
MBR, Sergey
prev parent reply other threads:[~2025-09-16 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 20:35 Sergey Shtylyov
2025-09-16 19:04 ` Sergey Shtylyov [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=ed43a751-3b02-46db-9fe1-da6c9f79fd80@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=bsdhenrymartin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=stable@vger.kernel.org \
--cc=sudeep.holla@arm.com \
--cc=viresh.kumar@linaro.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®