Electron has a use-after-free in offscreen shared texture release() callback
electron
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| electron npm |
|
|
electron
| Product | Affected | Fixed in |
|---|---|---|
| electron npm |
|
|
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. From 33.0.0-alpha.1 to before 39.8.5, 40.8.5, 41.1.0, and 42.0.0-alpha.5, apps that use offscreen rendering with GPU shared textures may be vulnerable to a use-after-free. Under certain conditions, the release() callback provided on a paint event texture can outlive its backing native state, and invoking it after that point dereferences freed memory in the main process, which may lead to a crash or memory corruption. Apps are only affected if they use offscreen rendering with webPreferences.offscreen: { useSharedTexture: true }. Apps that do not enable shared-texture offscreen rendering are not affected. To mitigate this issue, ensure texture.release() is called promptly after the texture has been consumed, before the texture object becomes unreachable. This vulnerability is fixed in 39.8.5, 40.8.5, 41.1.0, and 42.0.0-alpha.5.
From the CVE record · GitHub_M
Electron apps using offscreen rendering with GPU shared textures are vulnerable to a use-after-free. Calling a paint event texture’s release() callback after its backing native state is freed may crash the main process or corrupt memory. The input does not specify an attack path, authentication requirement, or user interaction.
Check apps using npm electron versions >=33.0.0-alpha.1 <39.8.5, >=40.0.0-alpha.1 <40.8.5, >=41.0.0-alpha.1 <41.1.0, or >=42.0.0-alpha.1 <42.0.0-alpha.5 with webPreferences.offscreen: { useSharedTexture: true }.