diff options
author | zeertzjq <zeertzjq@outlook.com> | 2024-08-02 05:58:20 +0800 |
---|---|---|
committer | zeertzjq <zeertzjq@outlook.com> | 2024-08-02 06:11:58 +0800 |
commit | a4bec30b7b2fa66a2db9d03f54e51dff58116465 (patch) | |
tree | 0b270084a35a96524377cb7624b0dc39d90e4629 /test/functional/lua/api_spec.lua | |
parent | 9f2d793068144ef92765fefd729b0eeffde11b7a (diff) | |
download | rneovim-a4bec30b7b2fa66a2db9d03f54e51dff58116465.tar.gz rneovim-a4bec30b7b2fa66a2db9d03f54e51dff58116465.tar.bz2 rneovim-a4bec30b7b2fa66a2db9d03f54e51dff58116465.zip |
vim-patch:9.0.2158: [security]: use-after-free in check_argument_type
Problem: [security]: use-after-free in check_argument_type
Solution: Reset function type pointer when freeing the function type
list
function pointer fp->uf_func_type may point to the same memory, that was
allocated for fp->uf_type_list. However, when cleaning up a function
definition (e.g. because it was invalid), fp->uf_type_list will be
freed, but fp->uf_func_type may still point to the same (now) invalid
memory address.
So when freeing the fp->uf_type_list, check if fp->func_type points to
any of those types and if it does, reset the fp->uf_func_type pointer to
the t_func_any (default) type pointer
closes: vim/vim#13652
https://github.com/vim/vim/commit/0f28791b215bd4c22ed580839409c2f7d39d8140
Co-authored-by: Christian Brabandt <cb@256bit.org>
Diffstat (limited to 'test/functional/lua/api_spec.lua')
0 files changed, 0 insertions, 0 deletions