Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

Devote Thursday to Xen and the art of hypervisor maintenance

Nine Xen fixes due to land, but don't panic: cloudy users have them already

The Xen Project will release nine patches on Thursday.

The Project gives each bug an “XSA” number and the 29th of October will see XSA 145 through 153 debut.

The patch run looks to be a tricky one, because the Project added XSA 143 and 144 to the list, but now lists them as unassigned. If you take a look at the outfit's vuln list, that's not happened before. The list has also grown in recent days: five patches were first listed.

We don't know what the patches are for, because the Xen Project's embargo rules mean that when it finds a nasty it keeps it secret for a while so that “significant distributors and operators of Xen … can prepare patched software in advance.”

That's a polite way of saying lots of big clouds like AWS use Xen, and it is a thoroughly bad idea for bugs to be made public before it and others like it can put patches in place.

For the rest of us, it means Thursday (US time) can safely be devoted to Xen and the art of hypervisor maintenance. ®

Similar topics

TIP US OFF

Send us news


Other stories you might like