Editor crash via freed buffer reference
Published Oct 7, 2024 · Updated Nov 3, 2025
Use-after-free in Vim before 9.1.0764 allows local users to crash the editor through a crafted BufWinLeave autocommand. Vim can free a buffer structure that a newly split window still references because do_ecmd does not reject a buffer marked as locked for deletion. Exploitation requires a deliberately configured autocommand that reopens the closing buffer and subsequent buffer-unload commands; the bounded result established upstream is an editor crash.
Summary
What happened
Use-after-free in Vim before 9.1.0764 allows local users to crash the editor through a crafted BufWinLeave autocommand. Vim can free a buffer structure that a newly split window still references because do_ecmd does not reject a buffer marked as locked for deletion. Exploitation requires a deliberately configured autocommand that reopens the closing buffer and subsequent buffer-unload commands; the bounded result established upstream is an editor crash.
The record
- CVE
- CVE-2024-47814
- Published
- Oct 7, 2024
- Updated
- Nov 3, 2025
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-416, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 7, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< v9.1.0764
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- vim_huaf_522 reproduction scriptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo