public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: CVE-2021-46966: ACPI: custom_method: fix potential use-after-free issue
Date: Thu, 29 Feb 2024 09:30:12 +0100	[thread overview]
Message-ID: <ZeBAlGNuNZNuCsE5@tiehlicka> (raw)
In-Reply-To: <2024022902-prancing-judgingly-c9ee@gregkh>

On Thu 29-02-24 06:22:34, Greg KH wrote:
> On Wed, Feb 28, 2024 at 05:14:22PM +0100, Michal Hocko wrote:
> > Hi,
> > this seems like another example of a reasonable fix with a very dubious
> > CVE IMHO. Allowing access to /sys/kernel/debug/acpi/custom_method to
> > anybody but trusted actor is a huge security problem on its own. I
> > really fail to see any value marking this clear bug fix as security
> > related.
> 
> It was picked because it was a use-after-free fix, AND it is part of the
> "import the GSD database into the CVE database" that the CVE project
> asked us to do.

OK I see. So now, does it make any sense to consider a bug fix in a
security sensitive interface (that is even locked down) a security fix?
-- 
Michal Hocko
SUSE Labs

  reply	other threads:[~2024-02-29  8:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2024022720-CVE-2021-46966-1469@gregkh>
2024-02-28 16:14 ` CVE-2021-46966: ACPI: custom_method: fix potential use-after-free issue Michal Hocko
2024-02-29  5:22   ` Greg Kroah-Hartman
2024-02-29  8:30     ` Michal Hocko [this message]
2024-02-29  8:40       ` Greg Kroah-Hartman

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=ZeBAlGNuNZNuCsE5@tiehlicka \
    --to=mhocko@suse.com \
    --cc=cve@kernel.org \
    --cc=gregkh@linuxfoundation.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