CVE-2025-22134: heap-buffer-overflow with visual mode in Vim < 9.1.1003
heap-buffer-overflow with visual mode in Vim < 9.1.1003
Other sources
When switching to other buffers using the :all command and visual mode still being active, this may cause a heap-buffer overflow, because Vim does not properly end visual mode and therefore may try to access beyond the end of a line in a buffer. In Patch 9.1.1003 Vim will correctly reset the visual mode before opening other windows and buffers and therefore fix this bug. In addition it does verify that it won't try to access a position if the position is greater than the corresponding buffer line. Impact is medium since the user must have switched on visual mode when executing the :all ex command. The Vim project would like to thank github user gandalf4a for reporting this issue. The issue has been fixed as of Vim patch v9.1.1003
— Debian
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-22134?
CVE-2025-22134 has a high severity due to the potential heap-buffer overflow that can lead to security exploits.
How do I fix CVE-2025-22134?
To fix CVE-2025-22134, update Vim to a version that is higher than 9.1.1003.
What are the affected versions of Vim for CVE-2025-22134?
Affected versions for CVE-2025-22134 include Vim versions up to 9.1.1003.
Can CVE-2025-22134 affect my system if I use Debian?
Yes, if you use Vim on Debian, versions up to 2:9.1.0967-2 are vulnerable to CVE-2025-22134.
What is the cause of CVE-2025-22134?
CVE-2025-22134 is caused by Vim not properly ending visual mode when switching buffers, leading to a heap-buffer overflow.