News Ryzen 3000 fix for 'Sinkclose' vulnerability arrives tomorrow — AMD reverses course and will patch Ryzen 3000 after all

[Admin]

AMD has changed course and provided a security patch for the Sinkclose vulnerability for Ryzen 3000 series desktop processors. The new update will arrive tomorrow, August 20.

Ryzen 3000 fix for 'Sinkclose' vulnerability arrives tomorrow — AMD reverses course and will patch Ryzen 3000 after all : Read more

 

[slightnitpick]

AMD had previously confirmed that it would patch the Sinkclose vulnerability on all its outgoing Ryzen CPUs, including the Zen 1 architecture chips.

The link you give doesn't support this statement:

https://www.tomshardware.com/pc-com...00-and-3000-will-not-get-patched-among-others

According to a statement given to Tom's Hardware, AMD said, "There are some older products that are outside our software support window."

 

[Bikki]

Performance hit? Count me out!

 

[Amdlova]

If they fix this will be good have tons of these machines worldwide less e-waste

 

[slightnitpick]

Performance hit?

Where did you get this?

 

[toaste]

Performance hit? Count me out!

The article doesn't mention a performance hit.

Sinkclose affects System Management Mode entry/exit. SMM exists from the time of the Intel 386SL, when there was no deletating things like timer interrupts or fan control to a microcontroller. Unfortunately modern UEFI vendors will still use it to implements things like power button presses, rtc interrupts, legacy usb keyboard interrupts and a few other things.

Any performant UEFI implementation will spend as few cycles in SMM as possible. Every clock cycle you spend in SMM is a direct reduction to performance of the OS/software.

If there even is a performance impact, it would be on the order of a few extra clock cycles to an already rare SMM exit. I expect it would be so small as to be impossible to even measure, though I look forward to anyone who benchmarks the before/after to try to quantify it.

 

[bobalazs]

Title is bad. Having english as a secondary language i can say

'Sinkclose' vulnerability arrives tomorrow​

​

should be fixed to

'Sinkclose' vulnerability fix arrives tomorrow​

 

[mitch074]

Title is bad. Having english as a secondary language i can say

'Sinkclose' vulnerability arrives tomorrow​

​

should be fixed to

'Sinkclose' vulnerability fix arrives tomorrow​

actually not, because it's the fix for the vulnerability that arrives - you'd repeat "fix", and that's a no-no.

 

[bobalazs]

WDYM? The Vulnerability is already there. The topic is about offering a fix for the vulnerability.
Sinkclose does not arrive tomorrow it's an active vulnerability already.
Sinkclose vulnerability fix arrives tomorrow is what makes sense.

 

[slightnitpick]

WDYM? The Vulnerability is already there. The topic is about offering a fix for the vulnerability.
Sinkclose does not arrive tomorrow it's an active vulnerability already.
Sinkclose vulnerability fix arrives tomorrow is what makes sense.

The full title is: Ryzen 3000 fix for 'Sinkclose' vulnerability arrives tomorrow — AMD reverses course and will patch Ryzen 3000 after all

Your correction would turn this into: Ryzen 3000 fix for 'Sinkclose' vulnerability fix arrives tomorrow — AMD reverses course and will patch Ryzen 3000 after all

Which implies that the fix itself needed a fix.

or at best: Ryzen 3000 for 'Sinkclose' vulnerability fix arrives tomorrow — AMD reverses course and will patch Ryzen 3000 after all

which is grammatically incorrect.

Though: Ryzen 3000 'Sinkclose' vulnerability fix arrives tomorrow — AMD reverses course and will patch Ryzen 3000 after all

No "for", would be a fine title as well.

My knowledge of grammatical structure isn't the best, but what I think is happening is that grammatically the original title makes "Ryzen 3000 fix" the object of the sentence and "Sinkclose vulnerability" the subject. While the last option, with fix after vulnerability, makes "Ryzen 3000" an adjective of "Sinkclose vulnerability".

 

[bobalazs]

The full title is: Ryzen 3000 fix for 'Sinkclose' vulnerability arrives tomorrow — AMD reverses course and will patch Ryzen 3000 after all

Your correction would turn this into: Ryzen 3000 fix for 'Sinkclose' vulnerability fix arrives tomorrow — AMD reverses course and will patch Ryzen 3000 after all

Which implies that the fix itself needed a fix.

or at best: Ryzen 3000 for 'Sinkclose' vulnerability fix arrives tomorrow — AMD reverses course and will patch Ryzen 3000 after all

which is grammatically incorrect.

Though: Ryzen 3000 'Sinkclose' vulnerability fix arrives tomorrow — AMD reverses course and will patch Ryzen 3000 after all

No "for", would be a fine title as well.

My knowledge of grammatical structure isn't the best, but what I think is happening is that grammatically the original title makes "Ryzen 3000 fix" the object of the sentence and "Sinkclose vulnerability" the subject. While the last option, with fix after vulnerability, makes "Ryzen 3000" an adjective of "Sinkclose vulnerability".

Sinkclose vulnerability fix arrives tomorrow is what i said
not
Ryzen 3000 for 'Sinkclose' vulnerability fix arrives tomorrow
you are grammatically incorrect sir.

​

'Sinkclose' vulnerability arrives tomorrow was the original title, that was bad.
P.S. the title had been fixed, so i was right all along...

 

[SethNW]

AMD just has to first ve crappy company and get much deserved negative reputation just to latter reverse course. Be it with pricing of graphic cards, negative reviews and then price drop. Or with here trying to sell idea of upgrading to newer generation, which backfired and now they are forced to do the right thing. All of that could have been good from beginning and AMD could not take hit to reputation, but nope, they got to try to be greedy. Though if you ask me, Ryzen isn't that old, they should have gone extra mile and patched it for all Ryzen CPUs. But it is more acceptable than it was. Like those aren't 10+ year old chips.

 

[slightnitpick]

Sinkclose vulnerability fix arrives tomorrow is what i said
not
Ryzen 3000 for 'Sinkclose' vulnerability fix arrives tomorrow
you are grammatically incorrect sir.

​

'Sinkclose' vulnerability arrives tomorrow was the original title, that was bad.
P.S. the title had been fixed, so i was right all along...

The below was captured 1 hour after article posting, and you didn't post your comment until a day later. Maybe something screwed up with the HTML at your end and clipped out the beginning of the title, but the title does not appear to have changed.

https://web.archive.org/web/2024081...es-course-and-will-patch-ryzen-3000-after-all

Ryzen 3000 fix for 'Sinkclose' vulnerability arrives tomorrow — AMD reverses course and will patch Ryzen 3000 after all​

News
By Aaron Klotz
published 1 hour ago
AMD has changed its mind and will add Sinkclose mitigation for Ryzen 3000 shortly.