this post was submitted on 12 Aug 2023
107 points (99.1% liked)

Steam Deck

14487 readers
692 users here now

A place to discuss and support all things Steam Deck.

Replacement for r/steamdeck_linux.

As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title

The following is a list of suggested flairs:
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.

Some more Steam Deck specific flairs:
[Boot Screen] - Custom boot screens/videos.
[Selling] - If you are selling your deck.

These are not enforced, but they are encouraged.

Rules:

Link to our Matrix Space

founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] autotldr@lemmings.world 25 points 1 year ago

This is the best summary I could come up with:


Last month when the Linux kernel was mitigated for Zenbleed as a CPU vulnerability affecting AMD Zen 2 processors, it turns out the Steam Deck APU was accidentally left without coverage.

An x86/urgent pull request sent out today for the Linux 6.5 kernel and for back-porting to current stable Linux kernel releases will extend the Zenbleed mitigation to protect Steam Deck gamers.

Most notable with these fixes is adding models 0x90-0x91 to the range of AMD Zenbleed-affected Zen 2 processors.

It looks like the Steam Deck's custom APU was just accidentally left out in the original Zenbleed patch.

This patch enables the Zenbleed fallback fix until a proper CPU microcode update is available for the Steam Deck.

Zenbleed (CVE-2023-20593) was disclosed last month after this data leakage vulnerability was discovered by a Google researcher.


I'm a bot and I'm open source!