AddressSanitizer:DEADLYSIGNAL
=================================================================
==4659==ERROR: AddressSanitizer: SEGV on unknown address 0x7f5b27b05000 (pc 0x0000004c779e bp 0x7ffd4ac1c930 sp 0x7ffd4ac1c840 T0)
==4659==The signal is caused by a READ memory access.
#0 0x4c779d in lj_err_run /home/yongheng/LuaJit_asan/src/lj_err.c:608:10
#1 0x4c821e in lj_err_callermsg /home/yongheng/LuaJit_asan/src/lj_err.c:724:3
#2 0x4c877f in err_argmsg /home/yongheng/LuaJit_asan/src/lj_err.c:756:3
#3 0x4c8886 in lj_err_argtype /home/yongheng/LuaJit_asan/src/lj_err.c:796:3
#4 0x4c89dd in lj_err_argt /home/yongheng/LuaJit_asan/src/lj_err.c:802:3
#5 0x60ec7a in lj_lib_checktab /home/yongheng/LuaJit_asan/src/lj_lib.c:270:5
#6 0x60f845 in lj_ffh_setmetatable /home/yongheng/LuaJit_asan/src/lib_base.c:131:14
#7 0x54a45a in lj_fff_fallback (/home/yongheng/LuaJit_asan/src/luajit+0x54a45a)
#8 0x4c78f1 in lj_err_run /home/yongheng/LuaJit_asan/src/lj_err.c:617:5
#9 0x4c7b54 in err_msgv /home/yongheng/LuaJit_asan/src/lj_err.c:632:3
#10 0x4c7928 in lj_err_msg /home/yongheng/LuaJit_asan/src/lj_err.c:638:3
#11 0x4d3799 in lj_state_growstack /home/yongheng/LuaJit_asan/src/lj_state.c:118:5
#12 0x5797e3 in lj_snap_restore /home/yongheng/LuaJit_asan/src/lj_snap.c:874:5
#13 0x52a685 in trace_exit_cp /home/yongheng/LuaJit_asan/src/lj_trace.c:793:13
#14 0x548bca in lj_vm_cpcall (/home/yongheng/LuaJit_asan/src/luajit+0x548bca)
#15 0x529161 in lj_trace_exit /home/yongheng/LuaJit_asan/src/lj_trace.c:863:13
#16 0x54a7d1 in lj_vm_exit_handler (/home/yongheng/LuaJit_asan/src/luajit+0x54a7d1)
#17 0x548555 in lj_BC_IFORL (/home/yongheng/LuaJit_asan/src/luajit+0x548555)
#18 0x7f5b2b6b11af (<unknown module>)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV /home/yongheng/LuaJit_asan/src/lj_err.c:608:10 in lj_err_run
==4659==ABORTING
The text was updated successfully, but these errors were encountered:
/cc roundup issues: #96821, #96828.
The diff upstream is fairly small, so let me trust Mike Pall on this.
Both versions get a pair of commits that seem to address the CVE
LuaJIT/LuaJIT#603
and 2.1 additionally gets one other small commit.
Hi, we found a crash in LuaJit
Version: 2.1. Git hash:
570e758ca7dd14f93efdd43d68cf8979c1d7f984POC:
Stack dump:
The text was updated successfully, but these errors were encountered: