It’s worth mentioning that those improvements are the result of the work of … @alimirjamali!
Some time ago, you told us that the publication might become irregular. In fact, it’s a daily newsletter now!? So the title should be something like: “Qubes OS updates Daily Review - Y2025-D186”
While I am not 100% sure, but there are some points about the CVE:
A compromised GPU kernel could potentially read local memory values from another kernel. Qubes OS GUI daemon/agent architecture does not allow direct access to GPU from GUI client qubes. So the entire CVE should be irrelevant for Qubes OS.
The CVE-2023-4969 was found in 2023. And according to Debian security tracker, it was fixed long ago with the 20250410-2 firmware (or even before that).
Correct! I use the workaround together with the “auto-login at boot” hack (also from the “Quick Quality of Life Improvements” thread), so I always get to the DE before all the auto-starts are launched.
@alimirjamali with the “list of new packages uploaded to Qubes OS repositories” which repositories exactly? Does it include testing repos, or is it only main ones that users will download from?
Thanks for your reply! It is indeed an old vulnerability, but AMD just started rolling out updates for client hardware in the last 2 months. There still isn’t even an update for Windows for quite a few hardware models. And there’s another vulnerability that also needs this same process isolation mode to be fixed: https://www.amd.com/en/resources/product-security/bulletin/amd-sb-6013.html
For Qubes default configuration it does not matter of course, unless you are able to use GPU passthrough. Though with the upcoming GPU acceleration feature, this might provide more security. I didn’t find any details on how to enable the process isolation mode though.
I don’t know when it was, but it was recent: Someone got the running qubes app to show when a disposable VM should be restarted/shutdown due to an updated template.