Announcement

Collapse
No announcement yet.

Linux Patched For New Intel "MMIO Stale Data" Vulnerabilities

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Linux Patched For New Intel "MMIO Stale Data" Vulnerabilities

    Phoronix: Linux Patched For New Intel "MMIO Stale Data" Vulnerabilities

    In addition to the Hertzbleed frequency scaling side-channel attack being made public today as part of "Patch Tuesday" and affecting both Intel and AMD CPUs, Intel is additionally disclosing a set of "MMIO Stale Data" vulnerabilities. The Linux kernel has already been patched for these new vulnerabilities affecting multiple generations of Intel CPUs from Rocket Lake back to Haswell X and Skylake...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    oh boy!

    Comment


    • #3
      For hertzbleed, Intel asked for embargo extension with no particular reason. And, by a pure coincidence, we have news about this actual Intel microcode bug diluted by the news about novel exploitation of general side-channels.

      Comment


      • #4
        One more flag to add to the command line...

        Comment


        • #5
          So just to be clear,
          Code:
          mitigations=off
          is no longer the only kernel parameter necessary to fully disable all mitigations (on hardware where it is safe to do so, like offline computers)? Or is
          Code:
          mmio_stale_data=off
          now also mandatory for this?

          Comment


          • #6
            Originally posted by OpenSourceAnarchist View Post
            So just to be clear,
            Code:
            mitigations=off
            is no longer the only kernel parameter necessary to fully disable all mitigations (on hardware where it is safe to do so, like offline computers)? Or is
            Code:
            mmio_stale_data=off
            now also mandatory for this?
            Code:
            mitigations=off
            disables all mitigations that can be disabled including this one, while
            Code:
            mmio_stale_data=off
            disables only this specific one.

            Basically you can choose which mitigations you want to disable (or configure since some have more parameters than just "off") by using their specific kernel parameters.

            Comment


            • #7
              I'd like to see Phoronix do the usual benchmarks with regards to this one.

              Comment


              • #8
                Is qemu/kvm affected?

                Comment

                Working...
                X