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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 19 Sep 2014 13:11:08 -0300 From: Henrique de Moraes Holschuh <hmh@....eng.br> To: Andy Lutomirski <luto@...capital.net> Cc: linux-kernel@...r.kernel.org, Borislav Petkov <bp@...en8.de>, H Peter Anvin <hpa@...or.com> Subject: Re: x86, microcode: BUG: microcode update that changes x86_capability On Thu, 18 Sep 2014, Andy Lutomirski wrote: > > [2] instantly segfaulting every running process using libpthread-2.19, > > as well as any other users of Intel TSX. > > https://bugs.launchpad.net/intel/+bug/1370352 > > > > And yes, this means we will kill support for microcode updates > > outside of the initramfs/early-initramfs, at least in Debian, > > and likely in Ubuntu. > > Given that there is exactly one microcode update like this (at least of > the sort that blows up userspace), I think that we should seriously > consider blacklisting just this particular microcode update once > userspace is running. This was just the first one. It is likely that there will be others. Anyway, IMHO kernel blacklists are of limited value for this kind of issue. Sure, we can add them to the microcode driver (*not* the early microcode driver) to protect the unwary after the fact, but the useful fast-reaction blacklisting will be done by the distros in userspace. In fact, a big thank-you to Canonical's QA process and to Felix Geyer, for raising the early alarm (https://bugs.launchpad.net/intel/+bug/1370352)... -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists