• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

AMD Struggles to Be Excluded from Unwarranted Intel VT Flaw Kernel Patches

Joined
Mar 10, 2010
Messages
11,878 (2.31/day)
Location
Manchester uk
System Name RyzenGtEvo/ Asus strix scar II
Processor Amd R5 5900X/ Intel 8750H
Motherboard Crosshair hero8 impact/Asus
Cooling 360EK extreme rad+ 360$EK slim all push, cpu ek suprim Gpu full cover all EK
Memory Corsair Vengeance Rgb pro 3600cas14 16Gb in four sticks./16Gb/16GB
Video Card(s) Powercolour RX7900XT Reference/Rtx 2060
Storage Silicon power 2TB nvme/8Tb external/1Tb samsung Evo nvme 2Tb sata ssd/1Tb nvme
Display(s) Samsung UAE28"850R 4k freesync.dell shiter
Case Lianli 011 dynamic/strix scar2
Audio Device(s) Xfi creative 7.1 on board ,Yamaha dts av setup, corsair void pro headset
Power Supply corsair 1200Hxi/Asus stock
Mouse Roccat Kova/ Logitech G wireless
Keyboard Roccat Aimo 120
VR HMD Oculus rift
Software Win 10 Pro
Benchmark Scores 8726 vega 3dmark timespy/ laptop Timespy 6506
To emphasize, the exploit is related to virtual memory, not virtualization, where kernel memory can be leaked to user-space. Virtualization will be one of several "victims" of such exploits, but virtualization is not the bug here.


Are they? Have you looked at the commit?



I think your article needs to be updated.


I think about two people in the thread referred to the commit, and quite possibly you were the only one to even read it, yet we have two long threads of people bashing Intel over something people don't even understand.

It should be obvious to anyone who spend five minutes checking the source that AMD have a bad bug here as well. The Intel bug is a design fault, simply because the engineers didn't take something into account. When you find a new type of defect in a design, it's not unlikely that competing designs might include similar mistakes, so it doesn't surprise me that AMD have a related bug of their own. Investigating such defects usually spawns new useful approaches to find more bugs.

Do you remember "Heartbleed"? It caused people to go look for similar problems and resulted in finding dozens of other bugs, some even worse.


Check the source, and you'll see it's specific to the x86 kernel.
Sweet so my home pc wont get the dreaded patch then is that what your saying , because the gist i have now is that

A. It affects only virtual servers indirectly if affected and only really data centers.

But

B. Everyone is getting a patch that might slow down crysis again causing chaos.

If both are true im still concerned, if just A then cheers mate im done here :)
 
Joined
Apr 12, 2013
Messages
6,728 (1.68/day)
Are you 100% sure that you know how AMD got into 8080 and x86? :)
Moreover, these companies used to be very close competitors for years. It ended in mid 2000s, but not because of any Intel's wrongdoing or a great conspiracy. AMD simply made some bad business decisions.
It wasn't the mid noughties, AMD was competitive till phenom II so right till 2010-11. Anyway the major reason (but not the only one) why AMD lost the x86 war was their own management's decision to not go 45-32nm quickly when they had the lead over Intel. Intel's bribes may have cost them a billion or two, in lost revenues per annum, but they lost a lot more due to Ruiz & Co.
 
Joined
Apr 21, 2010
Messages
562 (0.11/day)
System Name Home PC
Processor Ryzen 5900X
Motherboard Asus Prime X370 Pro
Cooling Thermaltake Contac Silent 12
Memory 2x8gb F4-3200C16-8GVKB - 2x16gb F4-3200C16-16GVK
Video Card(s) XFX RX480 GTR
Storage Samsung SSD Evo 120GB -WD SN580 1TB - Toshiba 2TB HDWT720 - 1TB GIGABYTE GP-GSTFS31100TNTD
Display(s) Cooler Master GA271 and AoC 931wx (19in, 1680x1050)
Case Green Magnum Evo
Power Supply Green 650UK Plus
Mouse Green GM602-RGB ( copy of Aula F810 )
Keyboard Old 12 years FOCUS FK-8100
To emphasize, the exploit is related to virtual memory, not virtualization, where kernel memory can be leaked to user-space. Virtualization will be one of several "victims" of such exploits, but virtualization is not the bug here.


It should be obvious to anyone who spend five minutes checking the source that AMD have a bad bug here as well. The Intel bug is a design fault, simply because the engineers didn't take something into account. When you find a new type of defect in a design, it's not unlikely that competing designs might include similar mistakes, so it doesn't surprise me that AMD have a related bug of their own. Investigating such defects usually spawns new useful approaches to find more bugs.

Someone answered :
No, this comment is referring to a different bug (and is why it is not redacted in the latest source). This workaround refers to preventing any executable code in the highest page and is done by reducing the constants below by the page size. KPTI is a separate workaround that is necessary to prevent leaking kernel memory during speculative execution on Intel's uarch, and is done by unmapping the kernel while executing userland.

https://www.reddit.com/r/Amd/comments/7nqwoe/_/ds4qihg
 
Joined
Dec 11, 2010
Messages
39 (0.01/day)
System Name NotAPotatoPC
Processor AMD Ryzen 5 5600G
Motherboard MSI B450 Gaming Plus
Cooling EVGA CLC 280MM
Memory 32 GB Corsair Vengeance DDR4 2400
Video Card(s) RTX 3080 FE
Storage A lot for just gaming... 1 TB SSD & 10 TB HDD
Display(s) Samsung CF591
Case Corsair Carbide
Audio Device(s) Corsair HS70 Bluetooth
Power Supply EVGA 850w Bronze
Mouse Hyper X Pulsefire Pro
Keyboard HyperX Alloy Origins Core
Software Windows 11
Benchmark Scores https://hwbot.org/user/figuretti
Joined
Dec 31, 2009
Messages
19,366 (3.72/day)
Benchmark Scores Faster than yours... I'd bet on it. :)
Just wait for the AT article gents... that will provide a bit more than a data scrape of news across three articles/threads. ;)
 
Joined
Apr 16, 2010
Messages
2,067 (0.41/day)
System Name The Stone that the Builders Refused / iJayo
Processor R5 1600/ R7 3700X
Motherboard Asrock AB350 Pro4 / Asus Rog Strix B450-F gaming
Cooling Cryorig M9 / Noctua NH-D14
Memory G skill 16 Gigs ddr4 / 16 gigs PNY ddr4
Video Card(s) Nvdia GTX 660 / Nvidia RTX 2070 Super
Storage 120gig 840 evo, 120gig adata sp900 / 1tb Mushkin M.2 ssd 1 & 3 tb seagate hdd, 120 gig Hyper X ssd
Display(s) 42" Nec retail display monitor/ 34" Dell curved 165hz monitor
Case Pink Enermax Ostrog / Phanteks Enthoo Evolv Tempered Glass edition
Audio Device(s) Altec Lansing Expressionist Bass/ M-Audio monitors
Power Supply Corsair450 / Be Quiet Dark Power Pro 650
Mouse corsair vengence M65 / Zalman Knossos
Keyboard corsair k95 / Roccat Vulcan 121
Software Window 10 pro / Windows 10 pro
Benchmark Scores meh... feel me on the battle field!
Intel's seems to be in the midst of a bad karma storm.......and their solution is:
1515000899375.png

....Amd can soooo capitalize on this......after they figure out how to not take a hit by it....
 
Joined
Aug 20, 2007
Messages
20,713 (3.41/day)
System Name Pioneer
Processor Ryzen R9 7950X
Motherboard GIGABYTE Aorus Elite X670 AX
Cooling Noctua NH-D15 + A whole lotta Sunon and Corsair Maglev blower fans...
Memory 64GB (4x 16GB) G.Skill Flare X5 @ DDR5-6000 CL30
Video Card(s) XFX RX 7900 XTX Speedster Merc 310
Storage 2x Crucial P5 Plus 2TB PCIe 4.0 NVMe SSDs
Display(s) 55" LG 55" B9 OLED 4K Display
Case Thermaltake Core X31
Audio Device(s) TOSLINK->Schiit Modi MB->Asgard 2 DAC Amp->AKG Pro K712 Headphones or HDMI->B9 OLED
Power Supply FSP Hydro Ti Pro 850W
Mouse Logitech G305 Lightspeed Wireless
Keyboard WASD Code v3 with Cherry Green keyswitches
Software Windows 11 Enterprise (legit), Gentoo Linux x64
I think your article needs to be updated.

No, it's not the same at all. I'm very familiar with the AMD high-register bug as it's linked to the linux "performance marginality"

It

a.) does not leak kernel memory, simply reboots the target system (this is the "bad things that'll happen")
b.) is fixed in epyc and TR solutions
 
Joined
Jul 18, 2017
Messages
575 (0.24/day)
So no performance drop from Windows Insiders. Linux taking the worst of things again.
 
Joined
Aug 20, 2007
Messages
20,713 (3.41/day)
System Name Pioneer
Processor Ryzen R9 7950X
Motherboard GIGABYTE Aorus Elite X670 AX
Cooling Noctua NH-D15 + A whole lotta Sunon and Corsair Maglev blower fans...
Memory 64GB (4x 16GB) G.Skill Flare X5 @ DDR5-6000 CL30
Video Card(s) XFX RX 7900 XTX Speedster Merc 310
Storage 2x Crucial P5 Plus 2TB PCIe 4.0 NVMe SSDs
Display(s) 55" LG 55" B9 OLED 4K Display
Case Thermaltake Core X31
Audio Device(s) TOSLINK->Schiit Modi MB->Asgard 2 DAC Amp->AKG Pro K712 Headphones or HDMI->B9 OLED
Power Supply FSP Hydro Ti Pro 850W
Mouse Logitech G305 Lightspeed Wireless
Keyboard WASD Code v3 with Cherry Green keyswitches
Software Windows 11 Enterprise (legit), Gentoo Linux x64
So no performance drop from Windows Insiders. Linux taking the worst of things again.

...In one game. That is not at all IO bound.
 

qubit

Overclocked quantum bit
Joined
Dec 6, 2007
Messages
17,866 (3.00/day)
Location
Quantum Well UK
System Name Quantumville™
Processor Intel Core i7-2700K @ 4GHz
Motherboard Asus P8Z68-V PRO/GEN3
Cooling Noctua NH-D14
Memory 16GB (2 x 8GB Corsair Vengeance Black DDR3 PC3-12800 C9 1600MHz)
Video Card(s) MSI RTX 2080 SUPER Gaming X Trio
Storage Samsung 850 Pro 256GB | WD Black 4TB | WD Blue 6TB
Display(s) ASUS ROG Strix XG27UQR (4K, 144Hz, G-SYNC compatible) | Asus MG28UQ (4K, 60Hz, FreeSync compatible)
Case Cooler Master HAF 922
Audio Device(s) Creative Sound Blaster X-Fi Fatal1ty PCIe
Power Supply Corsair AX1600i
Mouse Microsoft Intellimouse Pro - Black Shadow
Keyboard Yes
Software Windows 10 Pro 64-bit
Are you 100% sure that you know how AMD got into 8080 and x86? :)
Moreover, these companies used to be very close competitors for years. It ended in mid 2000s, but not because of any Intel's wrongdoing or a great conspiracy. AMD simply made some bad business decisions.
I did read about the beginnings and history of these two companies a long time ago. Did AMD get into x86, because IBM wanted a second source of x86 CPUs when they built their first PC maybe?

AMD has definitely made some bad business decisions and when you don't have as much resources in terms of money, fabs etc, the consequences of a bad decision is going to be more severe. I think it's a combination of this and Intel's dirty tricks against them which has lead to the current dominance of Intel over them. In fact, I seem to remember from that history that AMD were the underdog to Intel most of the time, right back to the early 70s.

And before anyone challenges me on this, no, I don't have reams of evidence of these dirty tricks by Intel, lol. It's just my opinion over reading many articles about these two over the years.

There was the Intel compiler thing which blew up for a minute a few years ago that hamstrung AMD processors...

The reality is, both have done shady things at times and both are sinners. If one can't agree to that, well, can't really help that. ;)
What, AMD aren't whiter than white? I'm shocked! :eek: Some people seem to think they are though and start to make excuses for them about their underperforming products, which tends to cause arguments in the forum. I dunno why people do this for companies who are just out to make a profit any way they can and have no loyalty to them whatsoever. And of course, AMD haven't paid for these people to shill for them...
 
Joined
Apr 26, 2008
Messages
229 (0.04/day)
System Name 3950X Workstation
Processor AMD Ryzen 9 3950X
Motherboard ASUS Crosshair VIII Impact
Cooling Cryorig C1 with Noctua NF-A12x15
Memory G.Skill F4-3600C16D-32GTZNC
Video Card(s) ASUS GTX 1650 LP OC
Storage 2 x Corsair MP510 1920GB M.2 SSD
Case Realan E-i7
Power Supply G-Unique 400W
Software Win 10 Pro
Benchmark Scores https://smallformfactor.net/forum/threads/the-saga-of-the-little-gem-continues.12877/
I think about two people in the thread referred to the commit, and quite possibly you were the only one to even read it, yet we have two long threads of people bashing Intel over something people don't even understand.

Sooo...


No, it's not the same at all. I'm very familiar with the AMD high-register bug as it's linked to the linux "performance marginality"

It

a.) does not leak kernel memory, simply reboots the target system (this is the "bad things that'll happen")
b.) is fixed in epyc and TR solutions

I guess it's you @efikkan who jumped the gun here...
 
Joined
Aug 20, 2007
Messages
20,713 (3.41/day)
System Name Pioneer
Processor Ryzen R9 7950X
Motherboard GIGABYTE Aorus Elite X670 AX
Cooling Noctua NH-D15 + A whole lotta Sunon and Corsair Maglev blower fans...
Memory 64GB (4x 16GB) G.Skill Flare X5 @ DDR5-6000 CL30
Video Card(s) XFX RX 7900 XTX Speedster Merc 310
Storage 2x Crucial P5 Plus 2TB PCIe 4.0 NVMe SSDs
Display(s) 55" LG 55" B9 OLED 4K Display
Case Thermaltake Core X31
Audio Device(s) TOSLINK->Schiit Modi MB->Asgard 2 DAC Amp->AKG Pro K712 Headphones or HDMI->B9 OLED
Power Supply FSP Hydro Ti Pro 850W
Mouse Logitech G305 Lightspeed Wireless
Keyboard WASD Code v3 with Cherry Green keyswitches
Software Windows 11 Enterprise (legit), Gentoo Linux x64
Joined
Feb 14, 2012
Messages
2,304 (0.52/day)
System Name msdos
Processor 8086
Motherboard mainboard
Cooling passive
Memory 640KB + 384KB extended
Video Card(s) EGA
Storage 5.25"
Display(s) 80x25
Case plastic
Audio Device(s) modchip
Power Supply 45 watts
Mouse serial
Keyboard yes
Software disk commander
Benchmark Scores still running
That twitter confirms it then. Yup, that's the one.
 
Joined
Aug 20, 2007
Messages
20,713 (3.41/day)
System Name Pioneer
Processor Ryzen R9 7950X
Motherboard GIGABYTE Aorus Elite X670 AX
Cooling Noctua NH-D15 + A whole lotta Sunon and Corsair Maglev blower fans...
Memory 64GB (4x 16GB) G.Skill Flare X5 @ DDR5-6000 CL30
Video Card(s) XFX RX 7900 XTX Speedster Merc 310
Storage 2x Crucial P5 Plus 2TB PCIe 4.0 NVMe SSDs
Display(s) 55" LG 55" B9 OLED 4K Display
Case Thermaltake Core X31
Audio Device(s) TOSLINK->Schiit Modi MB->Asgard 2 DAC Amp->AKG Pro K712 Headphones or HDMI->B9 OLED
Power Supply FSP Hydro Ti Pro 850W
Mouse Logitech G305 Lightspeed Wireless
Keyboard WASD Code v3 with Cherry Green keyswitches
Software Windows 11 Enterprise (legit), Gentoo Linux x64
That twitter confirms it then. Yup, that's the one.

Seems the exploit has officially been made open to the public.
 
Joined
Feb 14, 2012
Messages
2,304 (0.52/day)
System Name msdos
Processor 8086
Motherboard mainboard
Cooling passive
Memory 640KB + 384KB extended
Video Card(s) EGA
Storage 5.25"
Display(s) 80x25
Case plastic
Audio Device(s) modchip
Power Supply 45 watts
Mouse serial
Keyboard yes
Software disk commander
Benchmark Scores still running
Seems the exploit has officially been made open to the public.

The public post detailing it is six months old, if that is indeed the one. It all seems to line up. KPTI should kill that exploit.
 
Joined
Aug 20, 2007
Messages
20,713 (3.41/day)
System Name Pioneer
Processor Ryzen R9 7950X
Motherboard GIGABYTE Aorus Elite X670 AX
Cooling Noctua NH-D15 + A whole lotta Sunon and Corsair Maglev blower fans...
Memory 64GB (4x 16GB) G.Skill Flare X5 @ DDR5-6000 CL30
Video Card(s) XFX RX 7900 XTX Speedster Merc 310
Storage 2x Crucial P5 Plus 2TB PCIe 4.0 NVMe SSDs
Display(s) 55" LG 55" B9 OLED 4K Display
Case Thermaltake Core X31
Audio Device(s) TOSLINK->Schiit Modi MB->Asgard 2 DAC Amp->AKG Pro K712 Headphones or HDMI->B9 OLED
Power Supply FSP Hydro Ti Pro 850W
Mouse Logitech G305 Lightspeed Wireless
Keyboard WASD Code v3 with Cherry Green keyswitches
Software Windows 11 Enterprise (legit), Gentoo Linux x64
The public post detailing is six months old.

The difference is this is effectively a toolkit to utilize the exploit. There's a difference between saying "there's a problem" and utilizing it. It's about the difference between describing a gun and handing someone a loaded revolver.
 
Joined
Apr 12, 2013
Messages
6,728 (1.68/day)
The difference is this is effectively a toolkit to utilize the exploit. There's a difference between saying "there's a problem" and utilizing it. It's about the difference between describing a gun and handing someone a loaded revolver.
You're assuming there weren't criminals already exploiting this?
 
Joined
Aug 20, 2007
Messages
20,713 (3.41/day)
System Name Pioneer
Processor Ryzen R9 7950X
Motherboard GIGABYTE Aorus Elite X670 AX
Cooling Noctua NH-D15 + A whole lotta Sunon and Corsair Maglev blower fans...
Memory 64GB (4x 16GB) G.Skill Flare X5 @ DDR5-6000 CL30
Video Card(s) XFX RX 7900 XTX Speedster Merc 310
Storage 2x Crucial P5 Plus 2TB PCIe 4.0 NVMe SSDs
Display(s) 55" LG 55" B9 OLED 4K Display
Case Thermaltake Core X31
Audio Device(s) TOSLINK->Schiit Modi MB->Asgard 2 DAC Amp->AKG Pro K712 Headphones or HDMI->B9 OLED
Power Supply FSP Hydro Ti Pro 850W
Mouse Logitech G305 Lightspeed Wireless
Keyboard WASD Code v3 with Cherry Green keyswitches
Software Windows 11 Enterprise (legit), Gentoo Linux x64
You're assuming there weren't criminals already exploiting this?

There'll be a lot more with a public toolkit. There's a class of criminal who does his own exploits. This group is rather small. Then there's the "script-kiddies" and that' a large group indeed.

You're basically saying, that because the blueprints to a handgun are available, I should've been worried that people in their homes will start 3d-printing them. Yes, that eventually happened, but it required a bit more than blueprints, and yes it did signifigantly increase the number of unregistered people with access to firearms...
 
Joined
Feb 14, 2012
Messages
2,304 (0.52/day)
System Name msdos
Processor 8086
Motherboard mainboard
Cooling passive
Memory 640KB + 384KB extended
Video Card(s) EGA
Storage 5.25"
Display(s) 80x25
Case plastic
Audio Device(s) modchip
Power Supply 45 watts
Mouse serial
Keyboard yes
Software disk commander
Benchmark Scores still running
So the good news is that it's only unlimited read access, and not write access? :toast:
 
Joined
Apr 12, 2013
Messages
6,728 (1.68/day)
There'll be a lot more with a public toolkit. There's a class of criminal who does his own exploits. This group is rather small. Then there's the "script-kiddies" and that' a large group indeed.

You're basically saying, that because the blueprints to a handgun are available, I should've been worried that people in their homes will start 3d-printing them. Yes, that eventually happened, but it required a bit more than blueprints, and yes it did signifigantly increase the number of unregistered people with access to firearms...
That's why I asked how bad is it? I also would love to know the scope of the exploit & if there's any OS immune to this kind of attack, be it for Intel or possibly even AMD :confused:
Also there's possibly more than one exploit (uncovered) out there.
 
Joined
Aug 20, 2007
Messages
20,713 (3.41/day)
System Name Pioneer
Processor Ryzen R9 7950X
Motherboard GIGABYTE Aorus Elite X670 AX
Cooling Noctua NH-D15 + A whole lotta Sunon and Corsair Maglev blower fans...
Memory 64GB (4x 16GB) G.Skill Flare X5 @ DDR5-6000 CL30
Video Card(s) XFX RX 7900 XTX Speedster Merc 310
Storage 2x Crucial P5 Plus 2TB PCIe 4.0 NVMe SSDs
Display(s) 55" LG 55" B9 OLED 4K Display
Case Thermaltake Core X31
Audio Device(s) TOSLINK->Schiit Modi MB->Asgard 2 DAC Amp->AKG Pro K712 Headphones or HDMI->B9 OLED
Power Supply FSP Hydro Ti Pro 850W
Mouse Logitech G305 Lightspeed Wireless
Keyboard WASD Code v3 with Cherry Green keyswitches
Software Windows 11 Enterprise (legit), Gentoo Linux x64
That's why I asked how bad is it? I also would love to know the scope of the exploit & if there's any OS immune to this kind of attack, be it for Intel or possibly even AMD :confused:
Also there's possibly more than one exploit (uncovered) out there.

That's a very fair question, to be honest. I'd like to know as well.

So the good news is that it's only unlimited read access, and not write access? :toast:

Read access is actually far worse than you think. You can read passwords, keys, everything out of kernel memory.
 
Joined
Feb 14, 2012
Messages
2,304 (0.52/day)
System Name msdos
Processor 8086
Motherboard mainboard
Cooling passive
Memory 640KB + 384KB extended
Video Card(s) EGA
Storage 5.25"
Display(s) 80x25
Case plastic
Audio Device(s) modchip
Power Supply 45 watts
Mouse serial
Keyboard yes
Software disk commander
Benchmark Scores still running
Hah, I know, I was making a joke.
 
Last edited:
Top