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-next>] [day] [month] [year] [list]
Message-ID: <CAG48ez1=zOgmdsuE38HkG73EA4en+5QOTLTMZMe+PGcthhwt8g@mail.gmail.com>
Date:   Tue, 25 Sep 2018 14:46:32 +0200
From:   Jann Horn <jannh@...gle.com>
To:     Network Development <netdev@...r.kernel.org>,
        "David S. Miller" <davem@...emloft.net>
Cc:     Alexei Starovoitov <ast@...nel.org>,
        Daniel Borkmann <daniel@...earbox.net>, security@...nel.org
Subject: requesting stable backport of BPF security fix (commit dd066823db2ac4e22f721ec85190817b58059a54)

Hi!

Per the policy at Documentation/networking/netdev-FAQ.rst, I'm sending
this to netdev@ and davem, rather than stable@; with a CC to security@
because I believe that this is a security process issue.

Upstream commit dd066823db2ac4e22f721ec85190817b58059a54
("bpf/verifier: disallow pointer subtraction") fixes a security bug
(kernel pointer leak to unprivileged userspace). The fix has been in
Linus' tree since about a week ago, but the patch still doesn't appear
in Greg's linux-4.18.y linux-stable-rc repo, in Greg's 4.18
stable-queue, or in davem's stable queue at
http://patchwork.ozlabs.org/bundle/davem/stable/?state=* .

Please queue it up for backporting.

I am curious: Why was this not queued up for stable immediately? Or
was it, and I looked in the wrong place?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ