From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Michal Hocko <mhocko@suse.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org,
linux-cve-announce@vger.kernel.org, Tony Jones <tonyj@suse.de>
Subject: Re: CVE-2021-47543: perf report: Fix memory leaks around perf_tip()
Date: Thu, 13 Jun 2024 16:00:21 +0200 [thread overview]
Message-ID: <2024061337-delegator-chafe-bf6d@gregkh> (raw)
In-Reply-To: <Zma6fJmtaz8vgae2@tiehlicka>
On Mon, Jun 10, 2024 at 10:34:04AM +0200, Michal Hocko wrote:
> As far as I understand this is a bug in perf (userspace tool). This can
> occur when running 'perf report' which has a generally short lived
> lifespan. Is this really a CVE fix? What is the actual security threat?
You are correct, now rejected.
> Btw. CVE-2021-47545 is another one matcing the same pattern.
Thank you for noticing, also now rejected.
greg k-h
prev parent reply other threads:[~2024-06-13 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024052439-CVE-2021-47543-a01a@gregkh>
2024-06-10 8:34 ` CVE-2021-47543: perf report: Fix memory leaks around perf_tip() Michal Hocko
2024-06-13 14:00 ` Greg Kroah-Hartman [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=2024061337-delegator-chafe-bf6d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=tonyj@suse.de \
/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