Sunday , 25 March 2018
Home >> H >> Hardware >> Canonical reissues Meltdown and Spectre rags for Ubuntu after borkage

Canonical reissues Meltdown and Spectre rags for Ubuntu after borkage

OH RUDDY HECK. This whole Spectre/Meltdown spectacular isn’t accurately creation waves outward a tech attention and it’s being sensitively patched from within, yet inside, it’s like someone usually announced La La Land for Best Picture.

This time it’s Canonical, makers of Ubuntu. The association was one of a initial to patch a handling system. But afterwards it all went a bit wrong.

Users of 16.04 LTS Xenial Xerus started to protest that they, like some AMD users with Windows, weren’t means to foot after a refurbish (4.4.0-108) and could usually repair a problem with a rollback, citing a problem with a prior heart image.

No worries though. Ever discerning off a mark, Canonical has expelled a new patch – this one has a new heart picture 4.4.0-109.

The latest advisory reads:

“USN-3522-1 bound a disadvantage in a Linux heart to address
Meltdown (CVE-2017-5754). Unfortunately, that refurbish introduced
a retrogression where a few systems unsuccessful to foot successfully. This
update fixes a problem.

We apologize for a inconvenience.”

The Meltdown/Spectre vulnerabilities that have caused a reduction than happy new year for Intel in particular, that has an unique earthy smirch in many of a chips that can’t be fixed, usually patched during a program level, are causing an ongoing headache.

IBM is scheming to recover a possess rags and firmware upgrades, while AMD that has been influenced reduction seriously, should be entirely patched really quickly.

Nvidia has added that it, too is influenced and is operative to hurl out updates, and a Linux Mint distro is patched adult to heart 3.16. A repair for 3.17 and 3.18 is incoming so stay tuned.

It’s value remembering that, for example, if we have a gaming appurtenance with an Intel CPU, a Nvidia GPU and dual partitions, we need to get both rags for both partitions before you’re totally safe.

This is a problem – we can’t repair a chip. Every chip that is exposed will always be vulnerable. It’s how they correlate with a rest of a appurtenance that gets altered during a program level, and that will take some-more than usually one patch.

Thankfully, so far, it doesn’t seem that possibly disadvantage has been exploited. µ



  • <!–

  • Save this article

  • –>

==[ Click Here 1X ] [ Close ]==