104
this post was submitted on 25 Jun 2025
104 points (100.0% liked)
Linux
11450 readers
195 users here now
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The point is the Linux Kernel is covering the same security mitigations which make the CPU level ones redundant. If all users are using the Linux Kernel, why would it be an issue?
Depends on how you use your system if you have multiple users. CPU mitigations wont protect GPU workloads, and vice versa. If your CPU was mitigating GPU workloads, that would probably be a massive performance loss.
That’s not how this works.
The vulnerability is all on the CPU side. The GPU workloads being referenced are only vulnerable on the CPU instruction set used to pass workloads to the GPU.
Talking about CPU and GPU workloads as entirely separate in this context is misleading as the vulnerability is with CPU code execution that passes tasks to the GPU.
The GPU is not vulnerable to this particular attack, only the CPU is.
As you can see here impacted hardware is all CPU side, you can also read about how the proposed attacks work.
https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/spectre.html
Forgive me. Just trying to understand. How does the kernel flag
NEO_DISABLE_MITIGATIONShave any affect on the CPU? Seems to be targeted towards OpenCL and Level Zero, which are APIs to access GPU hardware directly.