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  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAEJ9NQd+SEEesyo54Em8cj_dRnYxkzC5fbRyU8pp2FeCiKJjcQ@mail.gmail.com>
Date: Wed, 28 Aug 2024 16:42:23 +0530
From: "Shanavas.K.S" <shanavasks@...il.com>
To: Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>, linux-kernel@...r.kernel.org
Subject: Re: intel CPU vulnerability NO_SSB whitelist for AIRMONT

 Thanks for the response.  Please create the patch from your side

Regards
Shanavas
> On Thu, Aug 8, 2024 at 12:32 AM Pawan Gupta
> <pawan.kumar.gupta@...ux.intel.com> wrote:
> >
> > On Wed, Aug 07, 2024 at 12:57:47PM +0530, Shanavas.K.S wrote:
> > > Hi Pawan Gupta
> > > Thanks for the comment. I have checked  IA32_ARCH_CAPABILITIES
> > > register but it is resulting in "unchecked MSR access error: RDMSR
> > > from 0x10a at rIP: 0xffffffff8286cc26". I am assuming the reason is
> > > the  MSR register is not available in our processor.
> >
> > Thats what it looks like.
> >
> > > Does it mean that NO_SSB should be added to the whitelist for
> > > INTEL_ATOM_AIRMONT_NP and INTEL_ATOM_AIRMONT_MID if these processors are
> > > not susceptible to cache speculation vulnerability?
> >
> > Correct, NO_SSB should be added to the whitelist for AIRMONT variants. Let
> > me know if you are planning to submit a patch for this. Otherwise, I will.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ