Researchers discover new security vulnerability in Intel processors

Comments

• sunnie@slrpnk.net ⁨3⁩ ⁨weeks⁩ ago

  No catchy name for the vulnerability? It can’t be that bad, then…

  source

  • rockSlayer@lemmy.blahaj.zone ⁨3⁩ ⁨weeks⁩ ago

    Let’s call it Son of Spectre

    source

    • b3an@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

      Bond, James Bond. Junior.

      source

      • -> View More Comments
  • x4740N@lemm.ee ⁨3⁩ ⁨weeks⁩ ago

    Wasnt CVE recently shut down, maybe that’s why it has no catchy name

    source

    • prettybunnys@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

      CVEs follow a naming convention, the exploit name is usually given by the researcher/hacker/whoever finds and documents it

      source
• domi@lemmy.secnd.me ⁨3⁩ ⁨weeks⁩ ago

  Intel has already deployed a fix for this in the 13th and 14th gen by permanently damaging the chip and crashing. Checkmate hackers.

  source
• kibiz0r@midwest.social ⁨3⁩ ⁨weeks⁩ ago

  Another day, another speculative execution vulnerability.

  source
• boreengreen@lemm.ee ⁨3⁩ ⁨weeks⁩ ago

  Intel gets punched again.

  source

  • msage@programming.dev ⁨3⁩ ⁨weeks⁩ ago

    Who, my good friend, fucking WHO still buys Intel for the servers? It sucks so hard, I don’t get it.

    source

    • anzo@programming.dev ⁨2⁩ ⁨weeks⁩ ago

      I bet other vendors implemented similar optimizations and have the same issues. That’s how it’s been in several occasions…

      source

      • -> View More Comments
    • Cocodapuf@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

      Well personally, I’ve been having a bear of a time trying to get my Ryzen machine to run correctly. I’m starting to think there just aren’t good options

      source

      • -> View More Comments
  • Krudler@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    I feel pretty duh here. That’s a great point.

    source
• ObviouslyNotBanana@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  Finally! I’ve been waiting to expose my processor

  source

  • DemandtheOxfordComma@lemmy.dbzer0.com ⁨3⁩ ⁨weeks⁩ ago

    Exhibitionist, eh?

    source

    • ObviouslyNotBanana@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

      Intel Exhibitionist

      source

      • -> View More Comments
• Cocodapuf@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  This sounds just like Spector/heartbleed. Haven’t we learned our lesson with speculative computation? I guess not…

  Well you know what they say, if it was a bad idea 10 fucking years ago, then let’s do it again!

  source

  • jbk@discuss.tchncs.de ⁨3⁩ ⁨weeks⁩ ago

    i mean just look at the performance hits with speculative execution off

    source
  • Bogus007@lemm.ee ⁨3⁩ ⁨weeks⁩ ago

    Intel has not learned, still making money on crap chips.

    source
  • gedhrel@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    With massive OOO pipelines, what’s the alternative?

    source
• naeap@sopuli.xyz ⁨3⁩ ⁨weeks⁩ ago

  Anyone having a link to a more technical (detailed) description?
  This is quite novice orientated and I’d be very interested on how it actually works. Is there anything already disclosed?

  source
• Blackmist@feddit.uk ⁨3⁩ ⁨weeks⁩ ago

  Can it be triggered from a browser?

  Because if not, it’s another non-issue issue for most people.

  I think after the last round of exploits, most of the browser makers made timers deliberately inaccurate enough to prevent it being used.

  source
• untakenusername@sh.itjust.works ⁨2⁩ ⁨weeks⁩ ago

  average Intel moment

  source
• pastermil@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

  Thankfully my Thinkpads from the last decade are not affected.

  source
• SoftestSapphic@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

  He look the US is putting hardware level vulnerabilities in our chips just like China does.

  We’re growing up so fast :'(

  source
• LodeMike@lemmy.today ⁨2⁩ ⁨weeks⁩ ago

  The so-called BPRC (Branch Predictor Race Conditions) emerge during a brief period of a few nanoseconds when the processor switches between prediction calculations for two users with different permissions, explains Sandro Rüegge, who has been examining the vulnerability in detail over the past few months.

  source