I won't complain since I have precisely the CPU model shown in the article picture.

I understand when a company just have to move forward and end support for their products. I also understand you have to prioritize business over consumer when addressing these issues. What I can't stand is a company thinking a +5 year old CPU doesn't deserve a security fix! All Ryzen CPUs should have this fixed, they were the turning point from FX processors and I'd say most of those are out of use today.

Silva:

I understand when a company just have to move forward and end support for their products. I also understand you have to prioritize business over consumer when addressing these issues. What I can't stand is a company thinking a +5 year old CPU doesn't deserve a security fix! All Ryzen CPUs should have this fixed, they were the turning point from FX processors and I'd say most of those are out of use today.

zen1 and zen1+ for embedded and servers should get it too. biggest issue is, zen1/1+ aren't supported by w11 officially because they had to sell new hardware (despite you may have an external tpm2.x module anyway.. and despite all we know that tpm doesn't add anything to security things on windows at all), zen2 however are still supported, sold and used as point of reference for many games. what is unreal is amd spent resources (money, time) as well bios/motherboard makers to implement fixes for far less important "security holes" like the logo fail and other stuffs, while this is much more serious issues and they aren't doing the same thing. while it's understandable to not support very old cpus anymore for security holes, they should have different time and extension support level depending how much serious is the security hole. A CVE 7.5 is much important than a 5.5 or lower score. Yes, CVSS3 still isn't perfect, still 7.5 and 5.5 is a huge difference.

Kaarme:

I won't complain since I have precisely the CPU model shown in the article picture.

Same here. Hopefully ASUS releases a BIOS update soon. The last update for my board was for AGESA 1.2.0 Ca.

AMD.... another Meltdown/Spectre style patch creating overhead, reducing CPU throughput.

floppyedonkey:

AMD.... another Meltdown/Spectre style patch creating overhead, reducing CPU throughput.

not sure about this, SMM isn't used much on running code. it may just rise the latency on SMM context switch (positive to negative rings context switch)

I have one question...

...does these security patches make any CPU performance slower?

Hilbert Hagedoorn:

AMD has announced it will release a patch addressing the 'Sinkclose' vulnerability in Ryzen 3000 desktop processors (codenamed Matisse) on August 20.This decision marks a reversal from the company's earlier stance, as outlined in its updated SMM Lock Bypass Security Bulletin. AMD Also Releases Security Patch for Sinkclose Vulnerability in Ryzen 3000 Processors

This is what happens when you contact a few partners and let them know amd is not meeting its security obligations. if Intel can release microcode patches down to nahalem in 2019, AMD can release agesa/microcode updates to zen+ in 2024.