Skip to main content
BlogLinodeVulnérabilités du CPU L1TF d'Intel & Linode

Vulnérabilités du processeur L1TF d'Intel et Linode


En début de semaine, Intel a révélé publiquement une nouvelle classe de vulnérabilités de processeurs connues sous le nom de L1 Terminal Fault (L1TF). Des variantes de L1TF affectent de nombreux environnements à locataire unique ou à locataires multiples, y compris certaines infrastructures de Linode et les Linodes eux-mêmes.

Nous avons commencé à prendre des mesures d'atténuation et nous prévoyons une atténuation complète de notre flotte dans les prochaines semaines. Nous pensons pouvoir y parvenir sans interrompre vos systèmes en fonctionnement et sans nécessiter de coordination de votre part. Cependant, la situation évolue encore et nous en saurons plus au fur et à mesure. Les premiers résultats de nos mesures d'atténuation sont encourageants.

Bien que cela protège notre côté des choses, vous devez vous assurer que vous utilisez un noyau Linux avec les mesures d'atténuation en place. Consultez notre guide sur la mise à jour de votre noyau.

Au fur et à mesure que nous progresserons dans nos efforts d'atténuation au cours des prochaines semaines, nous continuerons à fournir de plus amples informations sur notre blog. Restez à l'écoute !

Commentaires (8)

  1. Author Photo

    Thanks for the hard work in dealing with this. Though I am not sure it’s enough to just update the Kernel on OS side, need microcode updates – I guess from host node OS level too ?

    Wouldn’t the microcode updates require host node level reboots ?

  2. Christopher Aker

    You are correct! We’re able to transparently move VMs to patched infrastructure using live migrations.

  3. Author Photo

    Ah sweet – live migration feature is awesome. One of many reasons I have stuck with Linode for 4+ yrs now 🙂

  4. Author Photo

    What are your plans regarding HyperThreading?

    One of the things that has me shocked about L1TF is that there does not yet appear to be any publicly-available, complete mitigation to either of the major open-source hypervisors (KVM and Xen) that does not require HyperThreading to be disabled.

    L1TF is not fully mitigated if unrelated guests can run as hyper-siblings (or if an untrusted guest–which is all guests for a cloud VM provider–can run as a hyper-sibling of a hypervisor thread). Technically, this could be enforced by a scheduler, but the most unequivocal statement of a scheduler that will do so comes from, of all places, Microsoft, and therefore Azure (

    Google also indicates that individual cores are never concurrently shared between VMs ( Certainly, they have the wherewithal to pull this off with custom internal kernel changes, so there’s no particular reason to doubt them. (I didn’t find any clear statement from AWS on shared cores, but they already have their custom Nitro hypervisor, so plausibly they have a custom modification.)

    Unfortunately, the current docs applicable to KVM don’t provide any good solution for a cloud VM provider other than disabling HyperThreading:

    Am I wrong about this?

  5. Author Photo

    I too would like to know more about the hyperthreading story. We have multiple internal deployments of openstack and vmware that would suffer if we have to disable HT. Did Linode disable HT?

    I am very happy with Linode being able to live migrate things with no downtime to customers. That is a massive improvement over the past migration queues.

  6. Author Photo

    Thanks for implementing these security fixes.

    The new “live” migrations is certainly interesting – is this a new feature that you’re now able to use? It’s certainly much less painful than existing migration queues and forced downtime.

    Futhermore, will live migration be introduced for other server moves, such as upgrades and downgrades?

  7. Author Photo

    Our current plan for L1TF mitigation is to disable HyperThreading.

    Yes, live migrations are a feature that we are now able to use. We are evaluating the different use cases for this one, but currently it cannot be used for upgrades/downgrades with plan resizing.

  8. Author Photo

    Thanks for keeping us informed and patching the hosts. We appreciate the effort and due diligence. I’m sure these projects at large scale are never fun.

Laissez un commentaire

Votre adresse électronique ne sera pas publiée. Les champs obligatoires sont marqués d'un *.