• The new class of vulnerabilities in Intel processors arises from speculative technologies that anticipate individual computing steps.
  • Openings enable gradual reading of entire privilege memory contents of shared processor (CPU).
  • All Intel processors from the last 6 years are affected, from PCs to servers in data centres.
  • Blackmist@feddit.uk
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 hour 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.

  • Kairos@lemmy.today
    link
    fedilink
    English
    arrow-up
    1
    ·
    39 minutes 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.

  • Cocodapuf@lemmy.world
    link
    fedilink
    English
    arrow-up
    23
    arrow-down
    3
    ·
    edit-2
    16 hours ago

    This sounds just like Spectre/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!

  • Domi@lemmy.secnd.me
    link
    fedilink
    English
    arrow-up
    67
    arrow-down
    1
    ·
    1 day ago

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

  • boreengreen@lemm.ee
    link
    fedilink
    English
    arrow-up
    32
    ·
    edit-2
    1 day ago

    This vulnerability fundamentally undermines data security, particularly in the cloud environment where many users share the same hardware resources.

    Intel gets punched again.

    • msage@programming.dev
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      13 hours ago

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

      • Cocodapuf@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        7 hours 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

        • msage@programming.dev
          link
          fedilink
          English
          arrow-up
          5
          ·
          5 hours ago

          I’ve had numerous Ryzens, with 0 issues.

          Fewer Epics, but no issues either.

          What issues are you having?

          • Cocodapuf@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            4 hours ago

            Frequent crashing/freezing, especially at idle. Once the processor is under heavier load it’s fine, it’ll keep going smooth for hours. but at lower energy states the CPU is super unstable. It often takes me about a half hour just to get the thing up and running steady, very frustrating. Sometimes it likes to crash right as it’s changing load levels/c-State, so just as it finishes loading files for a game just as the first 3d frame is rendered. Or vice versa, it’ll crash about 15 seconds after the computer returns to mostly idle when you exit an application.

            I’ve tried a bunch of things, disabling c-states, manually setting dram timings, manually increasing power to various parts, enabling/disabling just about every relevant feature I can find. And of course looking for help online. I’m actually pretty sure the problem is in the motherboard, as one of the “fixes” I tried was going from a Ryzen 3600 to a 3800X, and the problem was the same.

            I’ve looked around and it’s an issue I have seen other people having, though it’s not very common. But there’s no consensus in the root of the problem. It does seem to be that it’s some interaction between the motherboard and cpu. It could plausibly be the power supply, but I think that’s pretty unlikely. The ram is fine.

            • x4740N@lemm.ee
              link
              fedilink
              English
              arrow-up
              2
              ·
              edit-2
              2 hours ago

              I don’t know if amd does this for your specific issue but you might have a problem had with amd driver conflicts, I had this issue and was going through great lengths to Tey and figure out what was causing this until the helpful people at toms hardware helped

              https://forums.tomshardware.com/threads/sporadic-bsods-in-windows-11-professional.3877530/#post-23472239

              Edit: also try turning off memory context restore and there was something about ram power levels thst might cause bsods of similar nature to other people but I don’t remember the bios setting name at this time unfortunately but am just leaving this here incase you figure out the name

              I’d also recomend making an account snd posting on tomshardware forums because they helped me figure out what was causing my own BSOD’s

              And run memtest86 and memtest86+ just to rule out bad ram

              Windows ram diagnostics is useless

              • x4740N@lemm.ee
                link
                fedilink
                English
                arrow-up
                1
                ·
                2 hours ago

                I really dislike how you’re so comfortable recommending RMA’ing a board when the person hasn’t provided logs / data

                Because that does nothing to solve the problem if it turns out that an RMA wasn’t needed

                Tech troubleshooting is a process of ruling things out and reading through information to narrow down to a probable cause and implementing a fix too see if it fixes the issue

                You have no information besides what they’ve already tried which is random things because they haven’t read log data or other information to help them figure out a cause

                • Nighed@feddit.uk
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  edit-2
                  59 minutes ago

                  I have to admit I didn’t read it through properly, but if it’s a problem with two CPUs then it’s probably a motherboard issue. (Or something g completely unrelated like ram)