You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When closing a window, the corresponding tagstack data will be cleared and freed. However a bit later, the quickfix list belonging to that window will also be cleared and if that quickfix list points to the same tagstack data, Vim will try to free it again, resulting in a double-free/use-after-free access exception.
Impact is low since the user must intentionally execute vim with several non-default flags, but it may cause a crash of Vim.
—
double-free in dialog_changed() 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 Vim project would like to thank github user SuyueGuo for reporting this issue.
The issue has been fixed as of Vim patch v9.1.0648
Patch(es)/Solution(s)
Update to >= 9.1.
The text was updated successfully, but these errors were encountered:
Affected package (and version)
vim
< 9.1.0648CVE ID(s)
CVE-2024-41957
Severity
Low
Other security advisory ID(s)
N/A
Description/References
use-after-free in tagstack_clear_entry() in Vim
Date: 01.08.2024
Severity: Low
CVE: CVE-2024-41957
CWE: Double Free (CWE-415)
When closing a window, the corresponding tagstack data will be cleared and freed. However a bit later, the quickfix list belonging to that window will also be cleared and if that quickfix list points to the same tagstack data, Vim will try to free it again, resulting in a double-free/use-after-free access exception.
Impact is low since the user must intentionally execute vim with several non-default flags, but it may cause a crash of Vim.
—
double-free in dialog_changed() in Vim < v9.1.0648
Date: 01.08.2024
Severity: Low
CVE:
CWE: Double Free (CWE-416)
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 Vim project would like to thank github user SuyueGuo for reporting this issue.
The issue has been fixed as of Vim patch v9.1.0648
Patch(es)/Solution(s)
Update to >= 9.1.
The text was updated successfully, but these errors were encountered: