Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Launching Atom with Nvidia Driver Requires the --in-process-gpu flag (which is a security vulnerability) #11

Open
Lonniebiz opened this issue Nov 26, 2023 · 0 comments
Labels
bug Something isn't working upstream bug on upstream

Comments

@Lonniebiz
Copy link

Lonniebiz commented Nov 26, 2023

The Atom 1.69.1 AppImage works in Debian 12 with default video card drivers, but after installing Nvidia drivers I get this error that prevents me from launching Atom:
[6712:1126/031759.008365:FATAL:gpu_data_manager_impl_private.cc(445)] GPU process isn't usable. Goodbye

I tried running Atom with this --disable-gpu:
./atom-v1.63.1-x86_64.AppImage --disable-gpu

But it produced the same error.

Finally, I found this:
atom/atom#23608

The --in-process-gpu argument got Atom launching again:
./atom-v1.63.1-x86_64.AppImage --in-process-gpu

However, running the GPU process within the same process as the application, as enabled by the --in-process-gpu flag, is considered less secure due to the increased risk of security vulnerabilities. In a typical setup, the GPU process is isolated in a separate process, which helps contain any potential security breaches within that process. If a vulnerability is exploited in the GPU process, the impact is limited to that process. However, when the GPU process runs within the main application process, any exploited vulnerability could have direct access to everything the main application can access, potentially leading to more severe security implications.

So, ideally, the source code should be modified to run GPU related tasks in a separate process.

@ferion11 ferion11 added bug Something isn't working upstream bug on upstream labels Dec 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working upstream bug on upstream
Projects
None yet
Development

No branches or pull requests

2 participants