Fix null pointer access in fast interpreter mode when configurable software bound check is enabled

The wasm_interp_call_func_bytecode is called for the first time with the empty module / exec_env to generate a global_handle_table. Before that happens though, the function checks if the module instance has bounds check enabled. Because the module instance is null, the program crashes. I added an extra check to prevent the crashes.

Author: loganek

core/iwasm/interpreter/wasm_interp_fast.c

@@ -1483,8 +1483,9 @@ wasm_interp_call_func_bytecode(WASMModuleInstance *module,
 #if !defined(OS_ENABLE_HW_BOUND_CHECK) \
     || WASM_CPU_SUPPORTS_UNALIGNED_ADDR_ACCESS == 0
 #if WASM_CONFIGURABLE_BOUNDS_CHECKS != 0
-    bool disable_bounds_checks = !wasm_runtime_is_bounds_checks_enabled(
-        (WASMModuleInstanceCommon *)module);
+    bool disable_bounds_checks = !module
+                                 && !wasm_runtime_is_bounds_checks_enabled(
+                                     (WASMModuleInstanceCommon *)module);
 #else
     bool disable_bounds_checks = false;
 #endif