5 ms·

Status in Ubuntu: https://people.canonical.com/~ubuntu-security/cve/2017/CVE-2017-6074.html https://people.canonical.com/~ubuntu-security/cve/2017/CVE-2...

• ptrincr 10y ago
  The below should be followed at the users own risk. Perhaps someone can confirm if the following is sane. For Ubuntu versions: Ubuntu 12.04.3 LTS Ubuntu 14.04.5 LTS The following should get you patched up, you will need a reboot though: sudo apt-get update sudo apt-get install linux-headers-3.13.0-110 linux-headers-3.13.0-110-generic linux-image-3.13.0-110-generic After reboot: uname -a Linux hostname 3.13.0-110-generic #157-Ubuntu Any Digital Ocean users may need to power down their droplet and switch the kernel to the following version: DigitalOcean GrubLoader v0.2 (20160714) Ubuntu Without this the new kernel may not be used.
  • lobster_johnson 10y ago
    Digital Ocean hasn't required that you change the kernel through the UI for some time now. Are you sure that's necessary?
    • jsamuel 10y ago
      It's only necessary for older servers (e.g. Ubuntu 12.04 and 14.04) where people haven't done this already.
      • vdloo 10y ago
        you can also use the API for this https://developers.digitalocean.com/documentation/v2/#change-the-kernel https://developers.digitalocean.com/documentation/v2/#change... for example for precise the kernel ID is 7515 for the "DigitalOcean GrubLoader v0.2 (20160714) Ubuntu" kernel. If you do this be sure to double-check the id by listing the kernels using the API though. You can also do this with libcloud using 'ex_change_kernel' from the 'DigitalOcean_v2_NodeDriver'