From 88c3d8900112b1798fa5084dd02de6a6fd06f365 Mon Sep 17 00:00:00 2001 From: zeertzjq Date: Sun, 16 Apr 2023 19:21:06 +0800 Subject: vim-patch:9.0.1143: invalid memory access with bad 'statusline' value (#23133) Problem: Invalid memory access with bad 'statusline' value. Solution: Avoid going over the NUL at the end. https://github.com/vim/vim/commit/7b17eb4b063a234376c1ec909ee293e42cff290c Co-authored-by: Bram Moolenaar --- src/nvim/statusline.c | 3 +++ 1 file changed, 3 insertions(+) (limited to 'src') diff --git a/src/nvim/statusline.c b/src/nvim/statusline.c index 05649e9b7f..feb67ad6fa 100644 --- a/src/nvim/statusline.c +++ b/src/nvim/statusline.c @@ -1373,6 +1373,9 @@ int build_stl_str_hl(win_T *wp, char *out, size_t outlen, char *fmt, char *opt_n // An invalid item was specified. // Continue processing on the next character of the format string. if (vim_strchr(STL_ALL, (uint8_t)(*fmt_p)) == NULL) { + if (*fmt_p == NUL) { // can happen with "%0" + break; + } fmt_p++; continue; } -- cgit