HWZ Forums

Login Register FAQ Mark Forums Read

All Intel processors affected by memory leaking vulnerability

Like Tree9Likes
Reply
 
LinkBack Thread Tools
Old 03-01-2018, 02:56 PM   #16
Supremacy Member
 
singupingu's Avatar
 
Join Date: Jan 2016
Posts: 5,219
Sound like good news for hackers lmao

Sent from Finally Unbanned using GAGT
Processor
AMD Ryzen 7 1700 w/ Wraith Spire LED (3.60GHz @ 1.25V)
Mainboard
Asus Strix X370-F Gaming (BIOS v3401)
Graphics Card
Asus Strix GTX 1080 OC Edition (OC-ed to 2.0GHz)
Memory
G.Skill Trident Z RGB 3600MHz C16 (3200MHz @ C14) 16GB Kit (2x8GB)
Display
Aftershock Prism+ Z270 (1440p, 60Hz, 5ms GTG, VA Panel)
Storage
Crucial MX300 750GB
Optical Storage
In Unicorn Land
Casing
NZXT S340 Elite Matte White (with 4x Corsair SP120 RGB)
PSU
EVGA G3 750W
Audio
Creative GigaWorks T20 Series II
OS
Windows 10 Home 64-bit

singupingu is online now   Reply With Quote
Old 03-01-2018, 04:29 PM   #17
Master Member
 
Join Date: Jan 2000
Posts: 4,891
The notes say AMD is not affected? No?
AMD CPUs do not have the bug, but the Linux patch has been coded to treat all x86 CPUs as buggy.

Unconfirmed news also reported the same assumption in the beta Windows patch which was pushed to fast ring Win10 users, where AMD EPYC supposedly took a 49% performance hit.

Last edited by chong; 03-01-2018 at 04:32 PM..
chong is offline   Reply With Quote
Old 03-01-2018, 04:44 PM   #18
Arch-Supremacy Member
 
wwenze's Avatar
 
Join Date: Dec 2002
Posts: 20,971
In before conspiracy to hurt AMD performance

Only affects heavy I/O operations anyway.
Processor
Venice 1.9ghz @ 1.1V on Ninja
Mainboard
MSI MS-7184 Amethyst
Graphics Card
Asus HD4770 Formula
Memory
2GB DDR400 (4x512MB rojak)
Display
Samsung SyncMaster 913V
Storage
WD3200KS on foam
Optical Storage
BenQ DW1650
Casing
Compaq Presario
PSU
Seasonic S12-430
Audio
Audigy -> Zhaolu D3 -> Yulong T-Amp -> Paradigm Atom Monitor v.1 (refoamed)
OS
Windows XP Pro w/SP2

wwenze is online now   Reply With Quote
Old 03-01-2018, 07:08 PM   #19
High Supremacy Member
 
haylui's Avatar
 
Join Date: Jul 2006
Posts: 27,100
In before conspiracy to hurt AMD performance

Only affects heavy I/O operations anyway.
News already mentioned AMD is not affected with the bug? No?
Processor
AMD Phenom II X6 1090T + CM V6GT + Corsair 2 x SP120 Perf
Mainboard
MSI 870-G54
Graphics Card
Sapphire HD7970
Memory
Kingston KVM 2x4GB 1333MHz
Display
Philips 220CW
Storage
60GB Kingston SSD+500GB WD Blue + 250GB seagate
Optical Storage
Samsung 22x DVDRW
Casing
ThermalTake Level 10GTS
PSU
FSP AURUM 92+ Series PT-650M
Audio
VIA VT1828S + Logitech X-230
OS
Windows 7 Pro

haylui is offline   Reply With Quote
Old 03-01-2018, 07:25 PM   #20
Arch-Supremacy Member
 
watzup_ken's Avatar
 
Join Date: Nov 2003
Posts: 15,089
So long story short, despite 2x increase in core count in 2017, fix in 2018 will negate improvements completely.
Processor
Ryzen 5 1600X
Mainboard
Gigabyte AB350M Gaming 3
Graphics Card
Zotac GTX 1050 Ti 4GB
Memory
Corsair Vengence LPX Red 16GB DDR4 3000
Display
Dell U2515H
Storage
Samsung 850 Pro & Evo 512GB/ WD Black 750GB
Optical Storage
NA
Casing
MATX Case
PSU
Seasonic G550
Audio
Realtek ALC887
OS
Windows 10 Pro 64bit

watzup_ken is online now   Reply With Quote
Old 03-01-2018, 08:49 PM   #21
Master Member
 
Join Date: Jan 2000
Posts: 4,891
News already mentioned AMD is not affected with the bug? No?
The performance drops are a result of the software patches being made to workaround the Intel CPU bug; the Intel CPU bug itself does not cause performance drops.

So yes, AMD does not have the bug. But because the software patches are currently being indiscriminately applied to all x86 machines, AMD machines which technically don't need the patches will also see performance drops after the impending software updates.
chong is offline   Reply With Quote
Old 03-01-2018, 09:39 PM   #22
Arch-Supremacy Member
 
Entry Level PC's Avatar
 
Join Date: Oct 2011
Posts: 18,014
Poor AMD, I thought they are going to HUAT gao gao for 2018 liao.
Processor
Intel Pentium 3805U @ 1.90GHz
Mainboard
MSI MS-B0961
Graphics Card
Intel HD Graphics
Memory
8.00GB Single-Channel DDR3
Display
DELL U2414H
Storage
931GB TOSHIBA MQ01ABD100
Casing
MSI Cubi
PSU
AC Adapter 65W
Audio
Intel Display Audio
OS
Windows 10 Pro 64-bit

Entry Level PC is offline   Reply With Quote
Old 04-01-2018, 08:24 AM   #23
Senior Member
 
lamesensei's Avatar
 
Join Date: Aug 2007
Posts: 1,373
The performance drops are a result of the software patches being made to workaround the Intel CPU bug; the Intel CPU bug itself does not cause performance drops.

So yes, AMD does not have the bug. But because the software patches are currently being indiscriminately applied to all x86 machines, AMD machines which technically don't need the patches will also see performance drops after the impending software updates.
pls do more research -

https://lkml.org/lkml/2017/12/27/2

AMD processors are not subject to the types of attacks that the kernel
page table isolation feature protects against. The AMD microarchitecture
does not allow memory references, including speculative references, that
access higher privileged data when running in a lesser privileged mode
when that access would result in a page fault.

Disable page table isolation by default on AMD processors by not setting
the X86_BUG_CPU_INSECURE feature, which controls whether X86_FEATURE_PTI
is set.

Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
---
arch/x86/kernel/cpu/common.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
index c47de4e..7d9e3b0 100644
--- a/arch/x86/kernel/cpu/common.c
+++ b/arch/x86/kernel/cpu/common.c
@@ -923,8 +923,8 @@ static void __init early_identify_cpu(struct cpuinfo_x86 *c)

setup_force_cpu_cap(X86_FEATURE_ALWAYS);

- /* Assume for now that ALL x86 CPUs are insecure */
- setup_force_cpu_bug(X86_BUG_CPU_INSECURE);
+ if (c->x86_vendor != X86_VENDOR_AMD)
+ setup_force_cpu_bug(X86_BUG_CPU_INSECURE);

fpu__init_system(c);
f hell this article about intel, intel fanboy still can turn around and shoot amd

Last edited by lamesensei; 04-01-2018 at 08:27 AM..
Processor
R7 1700
Mainboard
ASRock x370 Fatal1ty Gaming K4
Graphics Card
Gigabyte G1 Gaming GTX 1080
Memory
Cosair Vengeance LPX 16GB 3000 @ XMP 2400
Display
BENQ XL2720Z @ 144Hz
Storage
Samsung 960 PRO NVME 512GB + Samsung 850 EVO 512GB
Casing
NZXT S340 Elite
PSU
Cosair RM 650
Audio
Realtek 1120 + Logi MX Sound 2.0
OS
Windows 10 Home

lamesensei is offline   Reply With Quote
Old 04-01-2018, 08:41 AM   #24
High Supremacy Member
 
haylui's Avatar
 
Join Date: Jul 2006
Posts: 27,100
pls do more research -

https://lkml.org/lkml/2017/12/27/2



f hell this article about intel, intel fanboy still can turn around and shoot amd
so long is Intel has problem, then it is not user to worry. If AMD, i can't say the same.
Processor
AMD Phenom II X6 1090T + CM V6GT + Corsair 2 x SP120 Perf
Mainboard
MSI 870-G54
Graphics Card
Sapphire HD7970
Memory
Kingston KVM 2x4GB 1333MHz
Display
Philips 220CW
Storage
60GB Kingston SSD+500GB WD Blue + 250GB seagate
Optical Storage
Samsung 22x DVDRW
Casing
ThermalTake Level 10GTS
PSU
FSP AURUM 92+ Series PT-650M
Audio
VIA VT1828S + Logitech X-230
OS
Windows 7 Pro

haylui is offline   Reply With Quote
Old 04-01-2018, 08:46 AM   #25
Senior Member
 
Join Date: Sep 2007
Posts: 722
pls do more research -

https://lkml.org/lkml/2017/12/27/2



f hell this article about intel, intel fanboy still can turn around and shoot amd
First of all, that patch was only accepted 12 hours ago. At the time this thread was created, it was still uncommitted. Patches submitted to the kernel are never automatically accepted until they pass through a few maintainers, with Linus having the final say. A maintainer reviewing it has little impact on whether it is eventually committed.

And finally, that patch may still end up being rejected because Google claims its tests indicate AMD is also affected. Source: https://www.phoronix.com/scan.php?pa...CPU-Disclosure

Last edited by Rock-kun; 04-01-2018 at 08:51 AM..
Processor
AMD Athlon X2 7750 (I got ripped off! *pissed*)
Mainboard
Biostar GF8200 M2+ TE
Graphics Card
Onboard GeForce 8200...not too shabby.
Memory
2GB DDR2 667GHz SDRAM Kingston Value Ram
Display
19" Acer monitor
Storage
160GB Hitachi Deskstar SATA2
Optical Storage
SAmsung WriteMaster 16X
Casing
*unbranded*
PSU
AcBel 500W
Audio
Onboard. :(
OS
Debian Lenny (Linux kernel 2.6.26.2-AMD64) + Fedora 11

Rock-kun is offline   Reply With Quote
Old 04-01-2018, 08:46 AM   #26
Supremacy Member
 
Join Date: Mar 2002
Posts: 5,622
pls do more research -

https://lkml.org/lkml/2017/12/27/2



f hell this article about intel, intel fanboy still can turn around and shoot amd
I'm not sure why you're so quick to dismiss it as an Intel fan boy thing. Although there is a workaround that should be easy to implement, especially in Linux, there has been no confirmation that this is the approach taken for the windows patch.

Even the r/AMD subreddit is concerned that the initial patch will be an all encompassing one that will hit every single chip:

https://www.reddit.com/r/Amd/comments/7nqwoe/apparently_amds_request_to_be_excluded_from_the/?utm_source=reddit-android
Processor
2.0 GHz Intel Core 2 Duo
Graphics Card
Intel GMA 950 graphics processor
Memory
1.5 GB 667 MHz DDR2 Ram
Display
13.3 " TFT
Storage
80GB 5400 rpm Serial ATA hard disk drive
Optical Storage
24x slot-loading Combo drive (DVD-ROM/CD-RW)
OS
OS X Leopard

furyoo is online now   Reply With Quote
Old 04-01-2018, 08:52 AM   #27
Arch-Supremacy Member
 
wwenze's Avatar
 
Join Date: Dec 2002
Posts: 20,971
Sigh people trying to discuss and find discoveries and effect you label them as Intel fanbois... You (I'm not even to use the word "sir" even ironically) are the definition of fanboy

Tom's Guide has a very interesting way of rephrasing stuff...
"Major Security Flaws Exist on Intel, AMD, ARM CPUs"
"At 5 p.m., Daniel Gruss, a post-doctoral student in information security at the Technical University of Graz in Austria, came forward to announce Meltdown and Spectre. He told ZDNet's Zack Whittaker that "almost every system" based on Intel chips since 1995 was affected by the flaws. It turned out the problem was even worse."
https://www.tomsguide.com/us/intel-c...ews-26320.html

Could it be ever derivative from / copy of Pentium has this issue? Or just something that was convergent evolution? Or even an industry standard?
Just the concept of speculative execution? Any other factors involved?
__________________
You can accumulate experience, but whether you learn from it is a separate thing.

Last edited by wwenze; 04-01-2018 at 08:58 AM..
Processor
Venice 1.9ghz @ 1.1V on Ninja
Mainboard
MSI MS-7184 Amethyst
Graphics Card
Asus HD4770 Formula
Memory
2GB DDR400 (4x512MB rojak)
Display
Samsung SyncMaster 913V
Storage
WD3200KS on foam
Optical Storage
BenQ DW1650
Casing
Compaq Presario
PSU
Seasonic S12-430
Audio
Audigy -> Zhaolu D3 -> Yulong T-Amp -> Paradigm Atom Monitor v.1 (refoamed)
OS
Windows XP Pro w/SP2

wwenze is online now   Reply With Quote
Old 04-01-2018, 08:54 AM   #28
Senior Member
 
lamesensei's Avatar
 
Join Date: Aug 2007
Posts: 1,373
https://www.phoronix.com/scan.php?pa...isable-x86-PTI

While at the moment with the mainline Linux kernel Git tree AMD CPUs enable x86 PTI and are treated as "insecure" CPUs, the AMD patch for not setting X86_BUG_CPU_INSECURE will end up being honored.

The patch covered in the aforelinked article has not been merged through to Linus Torvalds' Git tree. Instead, as of a short time ago, is now living within the tip/tip.git tree. In there is also defaulting PAGE_TABLE_ISOLATION to on and other recent fixes around x86 Page Table Isolation (PTI) support.

But what remains to be seen is if this work will be pulled into Linux 4.15 Git or not. We're within three weeks of the executed debut of Linux 4.15.0 stable and it isn't clear if these tip changes will be requested to be pulled into Linux 4.15 or be postponed until the start of the Linux 4.16 kernel merge window, since the safe bulk of the x86 PTI work is already in Git master. Right now the branch name doesn't indicate it's in any fixes/urgent queue nor has there been any pull request yet asking Torvalds to take it into his repository: normally tip.git master is with material for linux-next.

So we'll have to see what ends up happening in the days ahead, but regardless, at least the "AMD patch" is now sitting within a known tree that will eventually flow into the mainline Linux tree whether it be 4.15 or 4.16.
plus extra salt for the lulz

https://lkml.org/lkml/2018/1/3/797

From Linus Torvalds <>
Date Wed, 3 Jan 2018 15:51:35 -0800
Subject Re: Avoid speculative indirect calls in kernel

On Wed, Jan 3, 2018 at 3:09 PM, Andi Kleen <andi@firstfloor.org> wrote:
> This is a fix for Variant 2 in
> https://googleprojectzero.blogspot.c...with-side.html
>
> Any speculative indirect calls in the kernel can be tricked
> to execute any kernel code, which may allow side channel
> attacks that can leak arbitrary kernel data.

Why is this all done without any configuration options?

A *competent* CPU engineer would fix this by making sure speculation
doesn't happen across protection domains. Maybe even a L1 I$ that is
keyed by CPL.

I think somebody inside of Intel needs to really take a long hard look
at their CPU's, and actually admit that they have issues instead of
writing PR blurbs that say that everything works as designed.

.. and that really means that all these mitigation patches should be
written with "not all CPU's are crap" in mind.

Or is Intel basically saying "we are committed to selling you ****
forever and ever, and never fixing anything"?

Because if that's the case, maybe we should start looking towards the
ARM64 people more.

Please talk to management. Because I really see exactly two possibibilities:

- Intel never intends to fix anything

OR

- these workarounds should have a way to disable them.

Which of the two is it?

Linus
and if it does affect amd i lose also y so mad?

Last edited by lamesensei; 04-01-2018 at 09:01 AM..
Processor
R7 1700
Mainboard
ASRock x370 Fatal1ty Gaming K4
Graphics Card
Gigabyte G1 Gaming GTX 1080
Memory
Cosair Vengeance LPX 16GB 3000 @ XMP 2400
Display
BENQ XL2720Z @ 144Hz
Storage
Samsung 960 PRO NVME 512GB + Samsung 850 EVO 512GB
Casing
NZXT S340 Elite
PSU
Cosair RM 650
Audio
Realtek 1120 + Logi MX Sound 2.0
OS
Windows 10 Home

lamesensei is offline   Reply With Quote
Old 04-01-2018, 08:55 AM   #29
Arch-Supremacy Member
 
wwenze's Avatar
 
Join Date: Dec 2002
Posts: 20,971
First of all, that patch was only accepted 12 hours ago. At the time this thread was created, it was still uncommitted. Patches submitted to the kernel are never automatically accepted until they pass through a few maintainers, with Linus having the final say. A maintainer reviewing it has little impact on whether it is eventually committed.

And finally, that patch may still end up being rejected because Google claims its tests indicate AMD is also affected. Source: https://www.phoronix.com/scan.php?pa...CPU-Disclosure
I think this episode just proves again the power of AMD's fanboy army, which managed to twist reality... for one day.
Would be the worst marketing spending if they weren't working for free.
__________________
You can accumulate experience, but whether you learn from it is a separate thing.
Processor
Venice 1.9ghz @ 1.1V on Ninja
Mainboard
MSI MS-7184 Amethyst
Graphics Card
Asus HD4770 Formula
Memory
2GB DDR400 (4x512MB rojak)
Display
Samsung SyncMaster 913V
Storage
WD3200KS on foam
Optical Storage
BenQ DW1650
Casing
Compaq Presario
PSU
Seasonic S12-430
Audio
Audigy -> Zhaolu D3 -> Yulong T-Amp -> Paradigm Atom Monitor v.1 (refoamed)
OS
Windows XP Pro w/SP2

wwenze is online now   Reply With Quote
Old 04-01-2018, 08:56 AM   #30
Senior Member
 
Join Date: Sep 2007
Posts: 722
Sigh people trying to discuss and find discoveries and effect you label them as Intel fanbois... You (I'm not even to use the word "sir" even ironically) are the definition of fanboy

Tom's Guide has a very interesting way of rephrasing stuff...
"Major Security Flaws Exist on Intel, AMD, ARM CPUs"
"At 5 p.m., Daniel Gruss, a post-doctoral student in information security at the Technical University of Graz in Austria, came forward to announce Meltdown and Spectre. He told ZDNet's Zack Whittaker that "almost every system" based on Intel chips since 1995 was affected by the flaws. It turned out the problem was even worse."
https://www.tomsguide.com/us/intel-c...ews-26320.html

Could it be ever derivative from / copy of Pentium has this issue? Or just something that was convergent evolution? Or even an industry standard?
I know Google claims ARM is also affected, but I still don't believe ARM has the computational power to drive datacentres and public clouds.
Processor
AMD Athlon X2 7750 (I got ripped off! *pissed*)
Mainboard
Biostar GF8200 M2+ TE
Graphics Card
Onboard GeForce 8200...not too shabby.
Memory
2GB DDR2 667GHz SDRAM Kingston Value Ram
Display
19" Acer monitor
Storage
160GB Hitachi Deskstar SATA2
Optical Storage
SAmsung WriteMaster 16X
Casing
*unbranded*
PSU
AcBel 500W
Audio
Onboard. :(
OS
Debian Lenny (Linux kernel 2.6.26.2-AMD64) + Fedora 11

Rock-kun is offline   Reply With Quote
Reply
Important Forum Advisory Note
This forum is moderated by volunteer moderators who will react only to members' feedback on posts. Moderators are not employees or representatives of HWZ. Forum members and moderators are responsible for their own posts.

Please refer to our Terms of Service for more information.


Thread Tools

Posting Rules

Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are On