From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2021-47093: platform/x86: intel_pmc_core: fix memleak on registration failure
Date: Mon, 4 Mar 2024 19:11:20 +0100 [thread overview]
Message-ID: <2024030414-CVE-2021-47093-ccd0@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
platform/x86: intel_pmc_core: fix memleak on registration failure
In case device registration fails during module initialisation, the
platform device structure needs to be freed using platform_device_put()
to properly free all resources (e.g. the device name).
The Linux kernel CVE team has assigned CVE-2021-47093 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.9 with commit 938835aa903a and fixed in 5.10.89 with commit 7a37f2e37069
Issue introduced in 5.9 with commit 938835aa903a and fixed in 5.15.12 with commit 9ca1324755f1
Issue introduced in 5.9 with commit 938835aa903a and fixed in 5.16 with commit 26a8b0943780
Please see https://www.kernel.org or 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-2021-47093
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/platform/x86/intel/pmc/pltdrv.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/7a37f2e370699e2feca3dca6c8178c71ceee7e8a
https://git.kernel.org/stable/c/9ca1324755f1f8629a370af5cc315b175331f5d1
https://git.kernel.org/stable/c/26a8b09437804fabfb1db080d676b96c0de68e7c
reply other threads:[~2024-03-04 18: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=2024030414-CVE-2021-47093-ccd0@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).