• NotNotMike@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 months ago

    I mean, I’m not much of a tinfoil hat, but this article feels extremely conveniently timed for Intel, who is currently going through a massive ordeal with their chips. Especially considering that the vulnerability is so extremely difficult to exploit that there’s borderline no story here for 99% of people but the headline will still drive clicks and drama.

    • TheGrandNagus@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      2 months ago

      Intel has literally done this, and stuff like it before.

      They back “independent” researchers who twist themselves in knots to make AMD look bad.

      Look up the multiple counts of bullshit from a “research group” called Principled Technologies.

      Sidenote: the guy who ran it was Ryan Shrout, who used to work for PC Perspective, and would usually give favourable reviews to Intel. After leaving Principled Technologies, he became head of technical marketing at… drumroll… Intel!

      Principled Technologies isn’t the only scam “independent researcher” Intel has set up or paid handsomely either.

    • Drathro@dormi.zone
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      Difficult to exploit, already in the process of being patched. Truly, the most breaking of news.

        • Passerby6497@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 months ago

          Most likely. Windows update (or the Linux equivalent on your platform) will download updated microcode to load at boot time to basically be a software patch for hardware issues. At least, that’s how it was explained when the original speculative execution flaw was discovered and Intel was releasing foxes and shit for it.

          • Amanda@aggregatet.org
            link
            fedilink
            English
            arrow-up
            1
            ·
            2 months ago

            and Intel was releasing foxes and shit

            I realise this is an autocorrect error, but it’s still funny 🦊

  • Avid Amoeba@lemmy.ca
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    2 months ago

    Requires kernel-level access. Also AMD is “releasing mitigations,” so is it “unfixable?”