Date: Tue, 2 Jan 2018 17:05:17 -0700 From: Warner Losh <imp@bsdimp.com> To: Michael Butler <imb@protected-networks.net> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Intel CPU design flaw - FreeBSD affected? Message-ID: <CANCZdfra8iS6ptP9Ct401sLum2mZi4dg0KTnkayQjUMbyDc4pQ@mail.gmail.com> In-Reply-To: <9dda0496-be16-35c6-6c45-63d03b218ccb@protected-networks.net> References: <9dda0496-be16-35c6-6c45-63d03b218ccb@protected-networks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
The register article says the specifics are under embargo still. That would make it hard for anybody working with Intel to comment publicly on the flaw and any mitigations that may be underway. It would be unwise to assume that all the details are out until the embargo lifts. Warner On Jan 2, 2018 4:13 PM, "Michael Butler" <imb@protected-networks.net> wrote= : > Has any impact assessment been made as to FreeBSD's exposure or > mitigation strategies? > > 'Kernel memory leaking' Intel processor design flaw forces Linux, > Windows redesign - The Register > > Other OSes will need an update, performance hits loom A fundamental > design flaw in Intel's processor chips has forced a significant redesign > of the Linux and Windows kernels to defang the chip-level security bug.= =E2=80=A6 > Programmers are scrambling to overhaul the open-source Linux kernel's > virtual memory system. Meanwhile, Microsoft is expected to publicly > introduce necessary changes to its Windows operating system in this > month's Patch Tuesday ... > > https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/ > > imb > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfra8iS6ptP9Ct401sLum2mZi4dg0KTnkayQjUMbyDc4pQ>