Editor crash via invalidated jump-mark pointer
Published Sep 22, 2022 · Updated May 23, 2025
Use-after-free in Vim before 9.0.0530 allows attackers to crash the editor by inducing a user to open a crafted file. In src/mark.c, movemark() retains a pointer to a jump-list mark while buflist_getfile() can run a BufEnter autocommand that invalidates that mark, then dereferences it. Exploitation requires user interaction and an untrusted Vim script or crafted file; confirmed impact is an application crash, while memory corruption or code execution is not established.
Summary
What happened
Use-after-free in Vim before 9.0.0530 allows attackers to crash the editor by inducing a user to open a crafted file. In src/mark.c, movemark() retains a pointer to a jump-list mark while buflist_getfile() can run a BufEnter autocommand that invalidates that mark, then dereferences it. Exploitation requires user interaction and an untrusted Vim script or crafted file; confirmed impact is an application crash, while memory corruption or code execution is not established.
The record
- CVE
- CVE-2022-3256
- Published
- Sep 22, 2022
- Updated
- May 23, 2025
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 22, 2022CVE publishedPublication date reported by the CVE source.
- May 23, 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=unspecified <9.0.0530
What conditions does exploitation require?
What is affected?
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
- Huntr mark-autocommand proof of conceptproof 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