linux-kernel - Re: [REGRESSION] 5.8-rc3: seccomp crash with Chromium, QtWebEngine and related browsers: seccomp-bpf failure in syscall 0072

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] [day] [month] [year] [list]

Message-ID: <202006290831.E9E695450@keescook>
Date:   Mon, 29 Jun 2020 08:32:55 -0700
From:   Kees Cook <keescook@...omium.org>
To:     Mel Gorman <mgorman@...hsingularity.net>
Cc:     Martin Steigerwald <martin@...htvoll.de>,
        LKML <linux-kernel@...r.kernel.org>,
        Andy Lutomirski <luto@...capital.net>,
        Will Drewry <wad@...omium.org>
Subject: Re: [REGRESSION] 5.8-rc3: seccomp crash with Chromium, QtWebEngine
 and related browsers: seccomp-bpf failure in syscall 0072

On Mon, Jun 29, 2020 at 04:08:07PM +0100, Mel Gorman wrote:
> On Mon, Jun 29, 2020 at 07:41:56AM -0700, Kees Cook wrote:
> > On Mon, Jun 29, 2020 at 11:08:10AM +0200, Martin Steigerwald wrote:
> > > Dear Andy, Kees, Will, dear kernel community,
> > > 
> > > With 5.8-rc3 there is a seccomp related crash which prevents Chromium and
> > > QtWebEngine from starting:
> > > 
> > > Bug 208369 - seccomp crash with Chromium, QtWebEngine and related browsers: seccomp-bpf failure in syscall 0072
> > > 
> > > https://bugzilla.kernel.org/show_bug.cgi?id=208369
> > > 
> > > Reverting to 5.8-rc2 fixes the issue.
> > 
> > Hi,
> > 
> > It looks like this is from e9c15badbb7b ("fs: Do not check if there is a
> > fsnotify watcher on pseudo inodes")
> > 
> > Currently being discussed here:
> > https://lore.kernel.org/lkml/7b4aa1e985007c6d582fffe5e8435f8153e28e0f.camel@redhat.com/#r
> > 
> 
> It's a definite problem. I've sent a revert but it hasn't hit lkml yet
> for whatever reason.

Okay, thanks! (Yeah, I think vger might be stuck?)

-- 
Kees Cook