From: Andy Lutomirski <luto@amacapital.net>
To: Sven Wegener <sven.wegener@stealer.net>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
"Richard Weinberger" <richard@nod.at>, "X86 ML" <x86@kernel.org>,
"Eric Paris" <eparis@redhat.com>,
"Linux Kernel" <linux-kernel@vger.kernel.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Borislav Petkov" <bp@alien8.de>,
"Toralf Förster" <toralf.foerster@gmx.de>,
stable <stable@vger.kernel.org>,
"Roland McGrath" <roland@redhat.com>,
"Josh Boyer" <jwboyer@fedoraproject.org>
Subject: Re: [PATCH] x86_32, entry: store badsys error code in %eax
Date: Mon, 21 Jul 2014 14:59:58 -0700 [thread overview]
Message-ID: <CALCETrU8xTGpOWONMnByAQo5TAqzutguw+L5_QW8K_iDe0EyeQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.11.1407202330420.31021@titan.int.lan.stealer.net>
On Sun, Jul 20, 2014 at 2:33 PM, Sven Wegener <sven.wegener@stealer.net> wrote:
> Commit 554086d ("x86_32, entry: Do syscall exit work on badsys
> (CVE-2014-4508)") introduced a subtle regression in the x86_32 syscall
> entry code, resulting in syscall() not returning proper errors for
> non-existing syscalls on CPUs not supporting the sysenter feature.
s/not supporting/supporting/
That means that this is IMO much worse than the other way around: all
newish 32-bit systems are affected.
Other than the typo and the missing Cc: stable:
Reviewed-and-tested-by: Andy Lutomirski <luto@amacapital.net>
--Andy
next prev parent reply other threads:[~2014-07-21 22:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 21:33 [PATCH] x86_32, entry: store badsys error code in %eax Sven Wegener
2014-07-20 22:07 ` H. Peter Anvin
2014-07-21 16:53 ` Andy Lutomirski
2014-07-21 17:20 ` H. Peter Anvin
2014-07-21 17:23 ` Andy Lutomirski
2014-07-21 21:59 ` Andy Lutomirski [this message]
2014-07-22 6:57 ` Sven Wegener
2014-07-22 8:26 Sven Wegener
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=CALCETrU8xTGpOWONMnByAQo5TAqzutguw+L5_QW8K_iDe0EyeQ@mail.gmail.com \
--to=luto@amacapital.net \
--cc=bp@alien8.de \
--cc=eparis@redhat.com \
--cc=hpa@zytor.com \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=roland@redhat.com \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=sven.wegener@stealer.net \
--cc=toralf.foerster@gmx.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).