A serious design flaw and security vulnerability has been discovered in Intel's CPUs that will require an update at the operating system level to fix, reports The Register. All modern computers with Intel chips from the last 10 years appear to be affected, including those running Windows, Linux, and macOS.
Full details on the vulnerability aren't yet known as the information is currently under embargo until later in the month. The Register has unearthed some data, however, and it seems the bug allows normal user programs to see some of the contents of the protected kernel memory.![]()
This means malicious programs can potentially, in a worst case scenario, read the contents of the kernel memory, which can include information like passwords, login keys, and more. It's not yet clear how severe the bug is, but The Register speculates that it's significant given the rapid changes being made to Windows and Linux.To fix the bug, the kernel's memory needs to be isolated from user processes using Kernel Page Table Isolation, which could cause a performance hit on some machines. According to The Register, Linux and Windows machines will see a 5 to 30 percent slowdown once the fix is in place.
It's not yet clear how Macs will be impacted, as there is little information available at this time. Software updates are in the works for Linux and Windows, and though not mentioned, Apple is also likely working on a fix for the issue.
Full details on what's known about the vulnerability can be found at The Register, and additional information will be available later this month when complete details on the design flaw are shared.
Article Link: Intel Chips Have Memory Access Design Flaw and Fix Could Lead to Performance Drop
It's more like giving someone the key to your home, and because of a mistake by the lock company, that key also opens your wine cellar, or your safe.Meh, that flaw is only an issue if someone has physical access to your machine and certain privileges already. That's like giving someone the key to your home and then blaming the lock company when they steal stuff.
If you read the license of your operating system carefully, you will find that you are not allowed to use any operating system for running a nuclear reactor, or anything else in potentially life threatening situations.An intel computer is used to store sensitive information, say, on police informants, or other vulnerable people. If it can be demonstrated that this flaw resulted in the deaths of those people (its not just a performance problem but a security one), then it's as big as an airbag issue. Just because computers don't have sharp edges or only sit on desks doesn't mean they can't hurt people.
For example if Intel's boss didn't know about this when he sold shares. Remember it wasn't Intel who found the problem.How is that not insider trading given today's news ?
There is no problem unless you have criminals attacking your computer. These processors work just fine unless criminals get involved.If it is a hardware flaw that impacts on performance, the products aren't fit for purpose and we're mis-sold. Most customers will be able to ask for exchanges, especially those in Europe. Don't put up with Intel fobbing you off with a software fix.
I worry this will not happen because they aren't really sold on merits of guaranteeing X number of executed instructions per second, only a particular clock frequency.If it is a hardware flaw that impacts on performance, the products aren't fit for purpose and we're mis-sold. Most customers will be able to ask for exchanges, especially those in Europe. Don't put up with Intel fobbing you off with a software fix.
Agreed, it's been a whole decade (!), god knows how many underground or state sponsored hackers who have known.how are they allowed an embargo period? That is borderline illegal.
Which processors exactly are affected?
Core2Duos?
Or i3/i5/i7 onwards?
Also the newly released 8th Gen core series?
Xeons?
I write software for MacOS and iOS, and I tell you this is not the case unless the software is written by an idiot.iOS is locked down and limited compared to MacOS. Designing software to run on both is going to mean limiting the said software to limitations of iOs.
No, the CPU speed doesn't drop. The CPU runs at the same speed. The CPU may have to do more work. How much more work, nobody knows.The bigger issue is that said patch will result in a 5-30% drop in CPU speed. It may not be a faulty airbag but it’s also not what was advertised on the box. It’s big trouble for Intel.
Since it is a security problem, there was no issue until someone realised there is an issue.So what are consumers supposed to do? I have 2 macs...
It’s taken 10 years to realize this issue???
Says who?Apple should use the IBM POWER9 processors for the new Mac Pro. I’ve heard they are vastly more secure than Intel and AMD processors.
30% slowdown? Queue the lawsuits!!! lol
Typhon:~ jeremy$ sysctl machdep.cpu.brand_string
machdep.cpu.brand_string: Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz
Typhon:~ jeremy$ sysctl machdep.cpu.features
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 FMA CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC MOVBE POPCNT AES PCID XSAVE OSXSAVE SEGLIM64 TSCTMR AVX1.0 RDRAND F16C
I wonder how this slow down will affect the cryptocurrency mining...
Which processors exactly are affected?
Core2Duos?
Or i3/i5/i7 onwards?
Also the newly released 8th Gen core series?
Xeons?
What is PCID?Apparently PCID can ameliorate the performance penalty, if apple decides to go that route.
You can find out if your cpu is recent enough by using the command line.
Code:Typhon:~ jeremy$ sysctl machdep.cpu.brand_string machdep.cpu.brand_string: Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz Typhon:~ jeremy$ sysctl machdep.cpu.features machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 FMA CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC MOVBE POPCNT AES PCID XSAVE OSXSAVE SEGLIM64 TSCTMR AVX1.0 RDRAND F16C
I write software for MacOS and iOS, and I tell you this is not the case unless the software is written by an idiot.