From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2022-50559: clk: imx: scu: fix memleak on platform_device_add() fails
Date: Wed, 22 Oct 2025 15:24:07 +0200 [thread overview]
Message-ID: <2025102206-CVE-2022-50559-e162@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
clk: imx: scu: fix memleak on platform_device_add() fails
No error handling is performed when platform_device_add()
fails. Add error processing before return, and modified
the return value.
The Linux kernel CVE team has assigned CVE-2022-50559 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.11 with commit 77d8f3068c63ee0983f0b5ba3207d3f7cce11be4 and fixed in 5.15.75 with commit 9209e6bab75d4008d9f4248c66008f3ffd24c931
Issue introduced in 5.11 with commit 77d8f3068c63ee0983f0b5ba3207d3f7cce11be4 and fixed in 5.19.17 with commit 43c589b7a187ef481b594317eaab8c8f269e4a68
Issue introduced in 5.11 with commit 77d8f3068c63ee0983f0b5ba3207d3f7cce11be4 and fixed in 6.0.3 with commit 05fe0b3d69b8e094db207648ab21cade56d71cd8
Issue introduced in 5.11 with commit 77d8f3068c63ee0983f0b5ba3207d3f7cce11be4 and fixed in 6.1 with commit 855ae87a2073ebf1b395e020de54fdf9ce7d166f
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-50559
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/clk/imx/clk-scu.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/9209e6bab75d4008d9f4248c66008f3ffd24c931
https://git.kernel.org/stable/c/43c589b7a187ef481b594317eaab8c8f269e4a68
https://git.kernel.org/stable/c/05fe0b3d69b8e094db207648ab21cade56d71cd8
https://git.kernel.org/stable/c/855ae87a2073ebf1b395e020de54fdf9ce7d166f
reply other threads:[~2025-10-22 13:25 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=2025102206-CVE-2022-50559-e162@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@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.