oss-security - Re: Lots of bugs in 32-bit x86 Linux entry code

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20191125175839.GB197885@espresso.pseudorandom.co.uk>
Date: Mon, 25 Nov 2019 17:58:39 +0000
From: Simon McVittie <smcv@...ian.org>
To: oss-security@...ts.openwall.com
Subject: Re: Lots of bugs in 32-bit x86 Linux entry code

On Mon, 25 Nov 2019 at 08:05:12 -0800, Andy Lutomirski wrote:
> It turns out that there are essentially no upstream development
> resources dedicated to x86_32 Linux. Perhaps unsurprisingly, it was
> badly broken.

To clarify, which of these do you mean?

A. IA-32 (uname -m: i?86) Linux kernels are buggy/vulnerable when running
   IA-32 (i?86-linux-*) user-space processes (which are the only user-space
   that these kernels support)

B. x86_64 (aka AMD64, uname -m: x86_64) Linux kernels are buggy/vulnerable
   when running IA-32 (i?86-linux-*) user-space processes, but not when
   running x86_64 (x86_64-linux-*) user-space processes

C. x86_64 (AMD64) Linux kernels are buggy/vulnerable when running x32
   (x86_64-linux-gnux32) processes

D. something else?

If I'm understanding correctly, you are reporting A, and only A?

Thanks,
    smcv

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.