this post was submitted on 25 Jul 2023
428 points (96.5% liked)

Technology

58507 readers
4700 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
L3s@lemmy.world
enu@lemm.ee
L4s@lemmy.world
fry@fry.gs
L3s@fry.gs
enu@lemmy.world
L4s@fry.gs
428
Encryption-breaking, password-leaking bug in many AMD CPUs could take months to fix (arstechnica.com)
submitted 1 year ago by Lanky_Pomegranate530@lemmy.world to c/technology@lemmy.world
94 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] Atemu@lemmy.ml 34 points 1 year ago (1 children)

Planned fix

December 2023

Yikes.

[–] evatronic@lemm.ee 29 points 1 year ago (1 children)

It's worth noting these are the firmware / microcode fixes.

There's already a software solution available,

There is a software workaround, you can set the chicken bit DE_CFG[9]. This may have some performance cost, and the microcode update is preferred.

source: https://www.openwall.com/lists/oss-security/2023/07/24/3

AMD has also already released a fix for the big boy - the EPYC processor.

[–] drdabbles@lemmy.world 1 points 1 year ago

The MSR bit is potentially a large performance loss and AMD recommends their partners not use it. In my tests is was 5-15% on EPYC depending on workload. "Some performance cost" is really hiding the reality of that bit.