Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop

In this Discussion

New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Xen PV vulnerability?

rskrsk Member, Host Rep
edited June 2012 in General

Hello guys,

Since we do not run any xen nodes, and only openvz - kindly check what I got below from PCsmart in regards to a vulnerability in the xen kernel ... just a heads up.

If you are not already aware, a vulnerability has recently been found which has the potential for a PV guest to escalate priviledges to the hypervisor.

If you are running on the standard Xen build included with CentOS5 / RHEL5, you can simply install the latest kernel with a "yum update" and you will be protected. However if you have a newer version of Xen installed which we typically do for performance reasons, you are vulnerable.

For customers on recurring management, please contact us and we will work with you to arrange a suitable time/date to carry out this work.

If we have done work for you recently and you would like to be upgraded, please also contact us and we will work something out.

We do have quite a few systems to get through, so your patience once you have submitted your ticket would be appreciated.

Many Thanks,

The PCSmart Team

Comments

This discussion has been closed.