linux-kernel - Re: CVE-2021-46966: ACPI: custom_method: fix potential use-after-free issue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZeBAlGNuNZNuCsE5@tiehlicka>
Date: Thu, 29 Feb 2024 09:30:12 +0100
From: Michal Hocko <mhocko@...e.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: cve@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: CVE-2021-46966: ACPI: custom_method: fix potential
 use-after-free issue

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