On macOS aarch64 with ubsan enabled binaries we see now, when running test compiler/jvmci/errors/TestInvalidCompilationResult :

/priv/jenkins/client-home/workspace/openjdk-jdk-weekly-macos_aarch64-opt/jdk/src/hotspot/share/asm/codeBuffer.cpp:984:27: runtime error: applying non-zero offset 18446744073709486080 to null pointer
    #0 0x106b5d658 in CodeBuffer::verify_section_allocation() codeBuffer.cpp:984
    #1 0x106b5d28c in CodeBuffer::~CodeBuffer() codeBuffer.cpp:128
    #2 0x106b5d834 in CodeBuffer::~CodeBuffer() codeBuffer.cpp:127
    #3 0x1072e7718 in CodeInstaller::install(JVMCICompiler*, long, bool, JVMCIObject, objArrayHandle, CodeBlob*&, JVMCINMethodHandle&, JVMCIObject, FailedSpeculation**, char*, int, JVMCIEnv*) jvmciCodeInstaller.cpp:847
    #4 0x1072fb818 in c2v_installCode0(JNIEnv_*, _jobject*, long, long, bool, _jobject*, _jobjectArray*, _jobject*, long, _jbyteArray*) jvmciCompilerToVM.cpp:1163
    #5 0x13746463c (<unknown module>)
    #6 0x13746090c (<unknown module>)

It is the code below in method "void CodeBuffer::verify_section_allocation()"
address tend = tstart + _total_size; <=== tstart seems to be nullptr in the reported case