From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49453: soc: ti: ti_sci_pm_domains: Check for null return of devm_kcalloc
Date: Wed, 26 Feb 2025 03:12:07 +0100 [thread overview]
Message-ID: <2025022659-CVE-2022-49453-9819@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
soc: ti: ti_sci_pm_domains: Check for null return of devm_kcalloc
The allocation funciton devm_kcalloc may fail and return a null pointer,
which would cause a null-pointer dereference later.
It might be better to check it and directly return -ENOMEM just like the
usage of devm_kcalloc in previous code.
The Linux kernel CVE team has assigned CVE-2022-49453 to this issue.
Affected and fixed versions
===========================
Fixed in 5.10.121 with commit 05efc4591f80582b6fe53366b70b6a35a42fd255
Fixed in 5.15.46 with commit 7cef9274fa1b8506949d74bc45aef072b890824a
Fixed in 5.17.14 with commit c4e188869406b47ac3350920bf165be303cb1c96
Fixed in 5.18.3 with commit 01ba41a359622ab256ce4d4f8b94c67165ae3daf
Fixed in 5.19 with commit ba56291e297d28aa6eb82c5c1964fae2d7594746
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2022-49453
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/soc/ti/ti_sci_pm_domains.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/05efc4591f80582b6fe53366b70b6a35a42fd255
https://git.kernel.org/stable/c/7cef9274fa1b8506949d74bc45aef072b890824a
https://git.kernel.org/stable/c/c4e188869406b47ac3350920bf165be303cb1c96
https://git.kernel.org/stable/c/01ba41a359622ab256ce4d4f8b94c67165ae3daf
https://git.kernel.org/stable/c/ba56291e297d28aa6eb82c5c1964fae2d7594746
reply other threads:[~2025-02-26 2:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2025022659-CVE-2022-49453-9819@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.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 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.