ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    New Hyperthreading Exploit Affects Intel CPUs, Maybe AMD

    News
    intel security exploit hyperthreading cpu ars technica
    2
    2
    702
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • mlnewsM
      mlnews
      last edited by

      Intel CPUs fall to new hyperthreading exploit that pilfers crypto keys

      Side-channel leak in Skylake and Kaby Lake chips probably affects AMD CPUs, too.

      Over the past 11 months, the processors running our computers, and in some cases phones, have succumbed to a host of attacks. Bearing names such as Meltdown and Spectre, BranchScope, TLBleed, and Foreshadow, the exploits threaten to siphon some of our most sensitive secrets—say passwords or cryptographic keys—out of the silicon microarchitecture in ways that can’t be detected or stopped by traditional security defenses. On Friday, researchers disclosed yet another leak that has already been shown to exist on a wide range of Intel chips and may also affect other makers, too.

      PortSmash, as the new attack is being called, exploits a largely overlooked side-channel in Intel’s hyperthreading technology. A proprietary implementation of simultaneous multithreading, hyperthreading reduces the amount of time needed to carry out parallel computing tasks, in which large numbers of calculations or executions are carried out simultaneously. The performance boost is the result of two logical processor cores sharing the hardware of a single physical processor. The added logical cores make it easier to divide large tasks into smaller ones that can be completed more quickly.

      More on Ars Technica...

      Emad RE 1 Reply Last reply Reply Quote 2
      • Emad RE
        Emad R @mlnews
        last edited by

        @mlnews

        There goes Ed25519

        Might as well stick to RSA 4096

        1 Reply Last reply Reply Quote 0
        • 1 / 1
        • First post
          Last post