From: Greg KH <gregkh@linuxfoundation.org>
To: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
Cc: stable@vger.kernel.org, bpf@vger.kernel.org,
Salvatore Bonaccorso <carnil@debian.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
Pavel Machek <pavel@denx.de>
Subject: Re: [PATCH 4.19 0/3] BPF fixes for CVE-2021-3444 and CVE-2021-3600
Date: Fri, 27 Aug 2021 16:38:20 +0200 [thread overview]
Message-ID: <YSj43Lpw9bilHuIn@kroah.com> (raw)
In-Reply-To: <20210827135533.146070-1-cascardo@canonical.com>
On Fri, Aug 27, 2021 at 10:55:30AM -0300, Thadeu Lima de Souza Cascardo wrote:
> The upstream changes necessary to fix these CVEs rely on the presence of JMP32,
> which is not a small backport and brings its own potential set of necessary
> follow-ups.
>
> Daniel Borkmann, John Fastabend and Alexei Starovoitov came up with a fix
> involving the use of the AX register.
>
> This has been tested against the test_verifier in 4.19.y tree and some tests
> specific to the two referred CVEs.
THanks for these, now queued up!
greg k-h
prev parent reply other threads:[~2021-08-27 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 13:55 [PATCH 4.19 0/3] BPF fixes for CVE-2021-3444 and CVE-2021-3600 Thadeu Lima de Souza Cascardo
2021-08-27 13:55 ` [PATCH 4.19 1/3] bpf: Do not use ax register in interpreter on div/mod Thadeu Lima de Souza Cascardo
2021-08-27 13:55 ` [PATCH 4.19 2/3] bpf: Fix 32 bit src register truncation " Thadeu Lima de Souza Cascardo
2021-08-27 13:55 ` [PATCH 4.19 3/3] bpf: Fix truncation handling for mod32 dst reg wrt zero Thadeu Lima de Souza Cascardo
2021-08-27 14:38 ` Greg KH [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=YSj43Lpw9bilHuIn@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=carnil@debian.org \
--cc=cascardo@canonical.com \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=pavel@denx.de \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.