mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Kees Cook <kees@kernel.org>,
	cve@kernel.org, linux-kernel@vger.kernel.org,
	linux-cve-announce@vger.kernel.org,
	Jinjie Ruan <ruanjinjie@huawei.com>
Subject: Re: CVE-2026-89603: entry: Fix seccomp bypass after ptrace with TSYNC
Date: Fri, 16 Oct 2026 08:30:21 +0200	[thread overview]
Message-ID: <2026101611-deputize-life-301e@gregkh> (raw)
In-Reply-To: <atEAhWWDDOo4kWSR@redhat.com>

On Thu, Oct 15, 2026 at 06:34:13PM +0200, Oleg Nesterov wrote:
> On 10/15, Kees Cook wrote:
> >
> > On Fri, Sep 11, 2026 at 09:44:52PM +0200, Greg Kroah-Hartman wrote:
> > > This race condition could allow an unprivileged process to execute
> > > a prohibited system call (e.g., execve) that the newly installed filter
> > > was intended to block, especially since the tracer might have modified
> > > the system call number during the ptrace stop.
> >
> > I'm disputing this one: please reject CVE-2026-89603. The fix is a fine
> > consistency change, but the flaw gave neither the tracer nor the tracee
> > anything they didn't already have.
> 
> Thanks Kees!
> 
> I fully agree with both points. The patch is fine, but it doesn't fix
> any security problem.

Now rejected, thanks for the review and letting us know!

greg k-h

      reply	other threads:[~2026-10-16  6:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2026091133-CVE-2026-89603-dad5@gregkh>
2026-10-15 16:25 ` Kees Cook
2026-10-15 16:34   ` Oleg Nesterov
2026-10-16  6:30     ` 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=2026101611-deputize-life-301e@gregkh \
    --to=gregkh@kernel.org \
    --cc=cve@kernel.org \
    --cc=kees@kernel.org \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=ruanjinjie@huawei.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®