Microsoft security update for CVE-2024-41965
🔗 CVE IDs covered (1)
📋 Microsoft's advisory
EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-41965. This page also shows what EchelonGraph holds for CVE-2024-41965, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.
🎯 Affected products5
- azl3 vim 9.0.2190-4 on Azure Linux 3.0
- azl3 vim 9.0.2190-6 on Azure Linux 3.0
- cbl2 vim 9.0.2121-4 on CBL Mariner 2.0
- cbl2 vim 9.0.2121-5 on CBL Mariner 2.0
- cbl2 vim 9.0.2121-5 on CBL-Mariner 2.0
✅ Updates Microsoft lists: 2 updates
2 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | 9.0.2121-4 |
| — | Security Update | 9.0.2190-4 |
🧭 EchelonGraph on CVE-2024-41965
- EchelonGraph score
- 4.2 MEDIUM
- CISA KEV
- Not listed
- Fix status
- A fix is available — apply it.
Description from the CVE record (CVE.org), as published by its numbering authority
Vim is an open source command line text editor. 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 issue has been fixed as of Vim patch v9.1.0648.
Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2024-41965, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).