CVE-2024-41957MediumMicrosoft CVSS 5.3CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

Microsoft security update for CVE-2024-41957

Published
September 10, 2024
Last Modified
—

🔗 CVE IDs covered (1)

CVE-2024-41957 →

📋 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-41957. This page also shows what EchelonGraph holds for CVE-2024-41957, 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 articleUpdateFixed build
—Security Update9.0.2121-4
—Security Update9.0.2190-4

🧭 EchelonGraph on CVE-2024-41957

EchelonGraph score
4.5 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. Vim < v9.1.0647 has double free in src/alloc.c:616. 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. The issue has been fixed as of Vim patch v9.1.0647

Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2024-41957, 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).

🔗 References (2)