mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Kees Cook <keescook@chromium.org>
Cc: Michal Hocko <mhocko@suse.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	cve@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: CVE-2023-52451: powerpc/pseries/memhp: Fix access beyond end of drmem array
Date: Thu, 29 Feb 2024 11:00:09 +0100	[thread overview]
Message-ID: <ZeBVqXvK3jFRRwQO@duo.ucw.cz> (raw)
In-Reply-To: <202402271029.FD67395@keescook>

[-- Attachment #1: Type: text/plain, Size: 555 bytes --]

Hi!

> > Does that mean that any potentially incorrect input provided by an admin is
> > considered CVE now?
> 
> Yes. Have you seen what USER_NS does? There isn't a way to know how
> deployments are using Linux, and this is clearly a "weakness" as defined
> by CVE. It is better to be over zealous than miss things.

Is it?

What is happening now is DoS on anyone who tries to use CVE
database... and on l-k users.

How do I get CVE number for that?

								Pavel
-- 
People of Russia, stop Putin before his war on Ukraine escalates.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      parent reply	other threads:[~2024-02-29 10:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2024022257-CVE-2023-52451-7bdb@gregkh>
2024-02-26 14:52 ` Michal Hocko
2024-02-26 15:06   ` Greg Kroah-Hartman
2024-02-26 15:25     ` Michal Hocko
2024-02-26 16:12       ` Greg Kroah-Hartman
2024-02-26 16:36         ` Michal Hocko
2024-02-27  5:14           ` Greg Kroah-Hartman
2024-02-27  8:51             ` Michal Hocko
2024-03-03 12:02               ` Michael Ellerman
2024-02-27  9:53             ` Jiri Kosina
2024-02-27 18:35       ` Kees Cook
2024-02-28 12:04         ` Michal Hocko
2024-02-28 17:12           ` Kees Cook
2024-02-29  8:22             ` Michal Hocko
2024-02-29  8:35               ` Greg Kroah-Hartman
2024-02-29  9:41                 ` Michal Hocko
2024-02-29 14:18                   ` Greg Kroah-Hartman
2024-02-29 15:08                     ` Kees Cook
2024-02-29 17:36                       ` Michal Hocko
2024-02-29 15:09                     ` Jiri Kosina
2024-02-29 16:09                       ` Sasha Levin
2024-02-29 17:11                         ` Jiri Kosina
2024-02-29 17:36                           ` Jiri Kosina
2024-02-29 18:32                             ` Greg Kroah-Hartman
2024-02-29 17:38                           ` Sasha Levin
2024-02-29 10:03                 ` Pavel Machek
2024-02-29 10:00         ` Pavel Machek [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=ZeBVqXvK3jFRRwQO@duo.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=cve@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.com \
    /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

all inboxes | Powered by JetHome®