this post was submitted on 13 Aug 2024
30 points (100.0% liked)

Hardware

589 readers
90 users here now

All things related to technology hardware, with a focus on computing hardware.


Rules (Click to Expand):

  1. Follow the Lemmy.world Rules - https://mastodon.world/about

  2. Be kind. No bullying, harassment, racism, sexism etc. against other users.

  3. No Spam, illegal content, or NSFW content.

  4. 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.

  5. Please try and post original sources when possible (as opposed to summaries).

  6. 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:

Icon by "icon lauk" under CC BY 3.0

founded 1 year ago
MODERATORS
 

cross-posted from: https://aussie.zone/post/12579772

Here we are - 3600 which was still under manufacture 2-3 years ago are not get patched. Shame on you AMD, if it is true.

top 8 comments
sorted by: hot top controversial new old
[–] Album@lemmy.ca 7 points 2 months ago (2 children)

Not patching the 3000 series seems like a big mistake because it was so popular. There's gotta be lots of those chips out in the wild. It's also a 5 year old chip. So I get not being able to go that far back.

Can anyone just release a chip without massive security flaws these days?

Can anyone just release a chip without massive security flaws these days?

Modern CPUs are far too complex to not inevitably have some sort of issue. You could make one without bugs, but it's going to perform HORRIBLY because all of those shortcuts are what make CPUs fast.

[–] Skyline969@lemmy.ca 0 points 2 months ago (2 children)

Apple? Or was there also a massive exploit found for Apple Silicon?

[–] rubikcuber@feddit.uk 6 points 2 months ago

Yep. GoFetch. Unpatchable hardware exploit on M1, M2 and M3 processors.

AS had a pretty big bug the other day.

[–] Blue_Morpho@lemmy.world 5 points 2 months ago (1 children)

This is really bad because unlike previous exploits, if you get owned, you have no way of ever knowing. No virus scan can detect it, no OS reinstall will remove it.

[–] Alphane_Moon@lemmy.world 3 points 2 months ago (1 children)

But the attacker/hacking tool needs admin/kernel access in the first place.

[–] Blue_Morpho@lemmy.world 1 points 2 months ago* (last edited 2 months ago)

Which all dangerous exploits already give. Next time there's a new published exploit for Linux or Windows, you could have been affected but will never know and will never be able to remove.