0

I found this script on GitHub that checks whether you susceptible to spectre and meltdown. Due to this script I am still susceptible. But I read that Ubuntu 16.04 got all patches on 9-th January. I use

Linux 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

UPD: I've done all apt update/upgrade magic but my kernel version is 4.13.0-26-generic. I've tested it on 2 machines. The update server is set to main server. Does anybody know why I do not see the latest kernel version?

UPD (about duplicate): It's not about official status of fixing this vulnerabilities on Ubuntu. It's about why I cannot install patches

danielleontiev
  • 385
  • 2
  • 19
  • That kernel was supposed to be the first for 16.04 released to patch for it. What does awk '/bugs/ {print ;exit}' /proc/cpuinfo return? I am running now 4.13.0-30-generic and it returns on that command: bugs : cpu_meltdown spectre_v1 spectre_v2 – Terrance Jan 16 '18 at 20:40
  • @Terrance your command returns bugs : cpu_insecure – danielleontiev Jan 16 '18 at 20:44
  • @Terrance I just run apt update, apt upgrade and apt-get dist-upgrade but it says there is nothing to do – danielleontiev Jan 16 '18 at 20:48
  • @Terrance, done, but nothing changes for me – danielleontiev Jan 16 '18 at 21:01
  • @Terrance of course. I have even done reboot after it – danielleontiev Jan 16 '18 at 21:09
  • @Terrance I do not use 4.10. My kernel version is 4.13.0-26-generic. The most strange thing why it is not 4.13.0-30-generic as on your computers. – danielleontiev Jan 16 '18 at 21:29
  • 1
    4.13.0-29-generic & now -30 are only in xenial -proposed repo, not yet released to main – doug Jan 16 '18 at 22:29
  • @doug thanks a lot, you rock. Do you know when it will be moved to main? – danielleontiev Jan 16 '18 at 22:35
  • 2
    No idea . People should only use -proposed selectively, ie. enable, update a specific package, disable. Though then they need to remember what they got from proposed. In this case you could get the new (-30) kernel, then disable -proposed & go on your merry way. However there is no imminent exploit/attacks around so I'd just let the updates come to you thru normal repos.. as there is a small chance the new kernel could cause issues for some.. – doug Jan 16 '18 at 22:44

0 Answers0