Good, it was a ridiculous position to take in the first place
this post was submitted on 20 Aug 2024
53 points (98.2% liked)
Hardware
464 readers
91 users here now
All things related to technology hardware, with a focus on computing hardware.
Rules:
-
Follow the Lemmy.world Rules - https://mastodon.world/about
-
Be kind. No bullying, harassment, racism, sexism etc. against other users.
-
No Spam, illegal content, or NSFW content.
-
Please stay on topic, adjacent topics (e.g. software) are fine if they are strongly relevant to technology hardware. Another example would be business news for hardware-focused companies.
-
Please try and post original sources when possible (as opposed to summaries).
-
If posting an archived version of the article, please include a URL link to the original article in the body of the post.
Some other hardware communities across Lemmy:
- Gaming Laptops
- Laptops
- History of Computing Hardware
- Linux Hardware
- Mechanical Keyboards
- Microcontrollers
- Monitors
- Single Board Computers
Icon by "icon lauk" under CC BY 3.0
founded 1 year ago
MODERATORS
Yeah, I couldn't believe it when I read that my 5 yo 3700X was not gonna get patched. I would have had a hard time buying another Ryzen when my platform upgrade is due in 2-3 years' time.
Edit: How will the fix be rolled out? Do I have to wait for a BIOS update?
This is my assumption, so I’ve been watching my motherboard’s OEM’s support site for an update to drop. I find it absolutely maddening that of the 20 or so articles I’ve read on this matter, not a single fucking one has mentioned how less educated users might go about patching this vulnerability. The tech journalists care about the clicks and literally nothing else.
Microcode is usually bundled with bios updates.
Thankfully, this vulnerability is difficult to exploit and requires hackers to use a different exploit to gain access to the computer's kernel before Sinkclose can be used to access the SMM.
Thank god there was no North Korean hacking group that just got exposed for exploiting zero-days for the past six months that gave them Kernel-level access, right guys?