Your question is a bit misleading. This is NOT caused by a Linux bug, there is no software bug involved in these segfaults. There was a different issue entirely that could be called a bug on Linux and BSD but those have both been fixed an are unrelated to this issue. The Kill Ryzen script also DOES NOT deliberately create a segfault. It is a merely a reasonable way to trigger them on a faulty processor (and also with other faulty hardware). The number of affected chips is unknown, just because there have been few reports doesn't mean few of the chips are faulty (not a lot of people run these kinds of workloads). The faults have also been exhibited running in Windows. Week 30+ processors given in response to RMA requests have mostly (maybe even all) not been affected, but that doesn't tell us anything about a week 30+ processor purchased from a store, we don't know if the chips provided through RMA have been tested to a higher standard/better binned, or if they are all fixed. So far AMD has NOT answered that. I'm not trying to fearmonger, but that's the situation so far. AMD will accept RMA for any affected chips though, so the worst case scenario when buying is the possibility of needing to take some time to do an RMA. I went through the RMA process, it is pretty quick and smooth so long as you have done the proper troubleshooting to isolate this issue.