Attention, the Meltdown hole is not fixed on 32-bit systems. Vulnerability is reported by Qualcomm

So it looks like the beginning of the year will not eventually be the result of a number of new innovations in the CES 2018, but a massive safety route that was discovered last year this year, rugged processors for PC and mobile, while the most challenging is the situation on Intel CPUs, which are contained in the overwhelming majority of computers. To these vulnerabilities called Spectre a Meltdown, we have learned two articles ( the first before the publisher, you would have a minimal second with official information). It does seem that virtual paper with them still prints out more, so they are going to discover serious “realities”. Probably the most remarkable thing about this is that Meltdown's error is not blamed as definitively as it did.

To be remembered: newly revealed vulnerabilities around the speculative execution of a study of the divorce > Lied to two groups. Error Specter affects at least theoretically most of the modern CPUs and exploits for it are certified on Intel, but also AMD, different ARMs, and also Power7 + 8th and 9th from IBM (this is officially confirmed they will need a firmware update and OS). Specter is considered to be something less or less as misleading as the second mistake Meltdown. Only Intel processors are suffering from the PC in the world (although it is not the case for AMD processors due to different architectures, VIA is not familiar with the situation ). This weakness makes it easy for you – including the javascript on the web site – to read data from the privileged memory of the operating system's junk.

Meltdown fix is ​​only for 64-bit operating system

Meltdown error (CVE-2017-5754 or so $ RoRogue Data Cache Load “) corrects the operating system updates that have already been issued (for Linux, MacOS 10.13 and Windows 7, SP1, 8.1 and 10). These are the patches that reduce power on Intel processors. But it looks like they do not fix the vulnerability of Meltdown up to 100% as we thought. The essence of this repair, called Kernel page-table isolation (KPTI), and Windows Shadowing Kernel, requires a 64-bit operating system and its large address space. This means that 32-bit operating systems are not applied or available.

 meltdown-text This is pretty damn sad and unfortunately this information is practically nobody. I found it on Twitter Alexe Ionescu of Widnows Internals . While Windows Update is being installed on 32-bit system targets against this group of attacks, the necessary measures against Meltdown are not in them.

In the picture you can see how the “pay” on a convertible tablet Asus Transformer Book T100TA where Windows 10 is installed in a 32-bit version and has been updated KB4056890 on Thursday. Microsoft's PowerShell Diagnostic Tool confirms that the Atom Z3740 processor requires a Meltdown Repair (Kernel VA Shadowing), but as you can see a red line of it, this support is not present in the operation

 Windows 10 32bit After Upgrade: The Meltdown Error Stops Unreadable. Asus Transformer Book T100TA 64bit Windows unfortunately does not support (exit from Microsoft's SpeculationControl diagnostic tool)
Windows 10 32bit after update: Meltdown error remains unreadable. Asus Transformer Book T100TA 64 bit Windows unfortunately does not support of Microsoft's SpeculationControl diagnostic tool )

This 32-bit computer is up to date after the Meltdown error It is exposed to the network by other PCs with 32-bit Windows (and Linux). If you have a problem here, consider installing a 64-bit operating system, otherwise you will remain vulnerable to Meltdown.

Unfortunately, this Å ™ the solution is not always possible, because many computers can not get 64-bit Windows for the best purpose. This is the case with the current Atom model models, which only have 32-bit UEFI, as far as 64-bit processors are concerned. Other times, users can be billed on 32-bit operating systems due to faulty drivers for some hardware. Or because they use 16-bit applications for very old versions of Windows or even DOS-support for 16-bit mode on a 64-bit platform does not exist. This means that for users, the Meltdown safety firewall on Intel processors remains open, and software repair will not work. It's all the more unfortunate that this problem is not enough to inform you that most users will most likely think that they have room after the update. Instead, they will have to rely on the fact that it is safe to collect the protection of the collection, for example, implemented before the web browsers

On the server, you have to turn on the patch yourself

By the way, with Meltdown, there is another note. Kernel VA Shadowing protection is not turned on on server windows in the default state due to performance. If you want to activate it as a Administrator, you need to learn it manually: See Microsoft Web site

 intel-pentium-silver-celeron-gemini-lake-bga-soc-processor-1600

(Polo) Meltdown on ARMs

What's wrong with Meltdown we have some other news. It does not pay that it is a problem with Intel. The same exploit or its fix can be misused on Apple's processors and also on the Cortex-A75. He has confirmed that his CPU Meltdown suffers, as well as Qualcomm. The one in Snapdragon 845 is an obviously modified Cortex-A75 aircraft that could probably be about them. But it is not excluded that they are vulnerable to some other rides such as Krait, Kryo or Falkor which the company has developed itself. Vulnerability should be treated as the Intelems of Linux or Android operating systems using the KPTI technique, but it is likely to be similar to a power failure

 qualcomm- Centriq-2400-1600 In addition, has been published that in a weaker form is the likelihood of Meltdown similar to other out-of-order jobs ARM Cortex, to A15, A57 and A72. In these cases, you may not be able to save the operating system session memory, but the data may still escape from the processor registers to which the common process would not have have access. It is also a weak spot, but it is unmanageable. ARM is of the opinion that there is no need for some special software measures. This is not a complete Meltdown error. This problem was identified directly by an ARM employee and may be found in other processors by other manufacturers, but no one was looking for it

Tags: