spice-vdagent: A flaw was found in spice-vdagent
CVE-2026-57965 is fixed in 3 products on 1 platform, first by spice-vdagent 0.22.1-1ubuntu0.1, released June 29, 2026. It is not reported as exploited. Patch Radar priority: Routine.
A flaw was found in spice-vdagent. A malicious or compromised SPICE host can trigger an integer overflow by sending a specially crafted message. This vulnerability can lead to a heap buffer overflow, causing the spice-vdagent daemon to crash and resulting in a Denial of Service (DoS) for the virtual machine. This issue requires the SPICE host to be untrusted or compromised for exploitation.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| spice-vdagent · Debian 12.15 (bookworm) | 0.22.1-3+deb12u1 | DEBIAN-CVE-2026-57965 | Jul 24, 2026 |
| spice-vdagent · Debian 14 | 0.23.0-3 | DEBIAN-CVE-2026-57965 | Jul 24, 2026 |
| spice-vdagent · Ubuntu 22.04.1 LTS (jammy) | 0.22.1-1ubuntu0.1 | spice-vdagent 0.22.1-1ubuntu0.1 | Jun 29, 2026 |
| spice-vdagent · Ubuntu 24.04.5 LTS (noble) | 0.22.1-4ubuntu0.1 | spice-vdagent 0.22.1-4ubuntu0.1 | Jun 29, 2026 |
| spice-vdagent · Ubuntu 26.04.1 LTS (resolute) | 0.23.0-1ubuntu0.1 | spice-vdagent 0.23.0-1ubuntu0.1 | Jun 29, 2026 |
| spice-vdagent · amzn 2023 | 0.22.1-7.amzn2023.0.1 | ALAS2023-2026-2061 | Aug 17, 2026 |
| spice-vdagent · opensuse-leap 16.0 | 0.22.1-160000.3.1 | OPENSUSE-SU-2026:21506-1 | Jul 31, 2026 |
| spice-vdagent · sles 15.6 | 0.22.1-150500.4.3.1 | SUSE-SU-2026:3485-1 | Aug 4, 2026 |
| spice-vdagent · sles 15.7 | 0.22.1-150500.4.3.1 | SUSE-SU-2026:3485-1 | Aug 4, 2026 |
| spice-vdagent · sles 16.0 | 0.22.1-160000.3.1 | SUSE-SU-2026:23109-1 | Jul 31, 2026 |
| spice-vdagent-debuginfo · amzn 2023 | 0.22.1-7.amzn2023.0.1 | ALAS2023-2026-2061 | Aug 17, 2026 |
| spice-vdagent-debugsource · amzn 2023 | 0.22.1-7.amzn2023.0.1 | ALAS2023-2026-2061 | Aug 17, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.