CVE-2024-41965: Vim < v9.1.0648 has a double-free in dialog_changed()
Vim < v9.1.0648 has a double-free in dialogchanged()
Other sources
Vim is an open source command line text editor. double-free in dialogchanged() in Vim < v9.1.0648. When abandoning a buffer, Vim may ask the user what to do with the modified buffer. If the user wants the changed buffer to be saved, Vim may create a new Untitled file, if the buffer did not have a name yet. However, when setting the buffer name to Unnamed, Vim will falsely free a pointer twice, leading to a double-free and possibly later to a heap-use-after-free, which can lead to a crash. The issue has been fixed as of Vim patch v9.1.0648.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
vimto a version that resolves this vulnerability.Fixed in v9.1.0648
Event History
Frequently Asked Questions
What is the severity of CVE-2024-41965?
CVE-2024-41965 has a medium severity rating due to the potential for a double-free vulnerability that could lead to application crashes.
How do I fix CVE-2024-41965?
To fix CVE-2024-41965, update Vim to version 9.1.0648 or later.
What versions of Vim are affected by CVE-2024-41965?
Vim versions before 9.1.0648 are affected by CVE-2024-41965.
What could happen if I don't address CVE-2024-41965?
If CVE-2024-41965 is not addressed, it may lead to crashes or data loss when managing modified buffers.
Is CVE-2024-41965 a remote exploitation risk?
CVE-2024-41965 does not have a direct remote exploitation risk but may affect user experience when editing files.