Kernel: 2.6.18.8-domU-linode7 (Latest 2.6)

Linode Staff

I've pushed out a new Xen kernel, 2.6.18.8-domU-linode7, which contains the vmsplice local root exploit fix.

"Latest 2.6" points to this kernel, so as long as you have that selected in your configuration profile just a reboot is needed.

-Chris

5 Replies

thank you,I really needed this.

I'm a litte confused since the kernel version reported in the Dashboard is "Latest 2.6 Series (2.6.18.8-domU-linode7)" but the VM itself reports:

$ uname -r
2.6.23.8-domU-linode2

which isn't in the list of current kernels unless it has been superseded since it hasn't been rebooted in a while.

That said, in Dashboard -> Linode Configuration Profiles -> Create Linode Configuration Profile the only options available for Kernel are:

2.6.18-domU-linode4

2.6.18.8-domU-linode5

2.6.18.8-domU-linode7

Latest 2.6 Series (2.6.18.8-domU-linode7)

Recovery - Finnix (kernel)

Didn't notice this with any of the old kernels, but on startup the console is getting spammed with:

modprobe: FATAL: Could not load /lib/modules/2.6.18.8-domU-linode7/modules.dep: No such file or directory

mkdir /lib/modules/$(uname -r)/ depmod -a

@mwalling:

mkdir /lib/modules/$(uname -r)/
depmod -a


Probably not (Gentoo):

edison ~ # mkdir /lib/modules/$(uname -r)/ -p
edison ~ # depmod -a
depmod: QM_MODULES: Function not implemented

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct