The issue is related to a possible use-after-free problem in the kprobes registration of the Linux kernel. When unloading a module, its state changes, and if `is module text address()` and ` module text address()` are used separately, there is a chance that the first one succeeds but the next one fails because the module's state becomes MODULE STATE UNFORMED between these operations. In the `check kprobe address safe()` function, if the second ` module text address()` fails, it is ignored because it expected a kernel text address, but it may have failed simply because the module's state has been changed to MODULE STATE UNFORMED. This can cause `arm kprobe()` to try to modify a non-existent module text address, resulting in a use-after-free issue.