kernel panic occurred at _sisevt_check_fopmap() during boot process

Issue

• Kernel panic occurred at _sisevt_check_fopmap() during a boot process.
  • The following panic message can be observed.

[    4.711411] BUG: unable to handle kernel paging request at ffffffff97837ff8
[    4.715930] PGD 102a13067 P4D 102a13067 PUD 102a14063 PMD 80000001022000e1
[    4.720347] Oops: 0003 [#1] SMP PTI
[    4.723413] CPU: 3 PID: 761 Comm: systemd-udevd Tainted: P            E    --------- -  - 4.18.0-305.el8.x86_64 #1
...
[    4.734983] RIP: 0010:_sisevt_check_fopmap+0x2f9/0x590 [sisevt]
[    4.738992] Code: 00 4c 89 2c d5 60 8e 66 c0 49 89 44 24 38 e8 be 0e 00 00 48 83 7d 78 00 48 c7 c2 90 5c 65 c0 48 c7 c1 e0 5c 65 c0 48 0f 44 d1 <48> 89 55 78 85 c0 0f 85 ae 01 00 00 48 c7 c7 10 81 66 c0 48 83 05
[    4.751191] RSP: 0018:ffffb8ccc1fcbe70 EFLAGS: 00010246
[    4.754943] RAX: 0000000000000000 RBX: ffffa0786e75c9c8 RCX: ffffffffc0655ce0
[    4.759447] RDX: ffffffffc0655ce0 RSI: 80000001022000e3 RDI: 80000001022000e3
[    4.763910] RBP: ffffffff97837f80 R08: ffffa074800005e0 R09: 0000000000000000
[    4.768402] R10: 0000000000000007 R11: ffffa0786d1d7800 R12: ffffa0786e75c9c0
[    4.772905] R13: ffffa0786e75c9f0 R14: 0000000000000000 R15: 0000000000000000
[    4.777435] FS:  00007fc159017180(0000) GS:ffffa0789d580000(0000) knlGS:0000000000000000
[    4.783869] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    4.787830] CR2: ffffffff97837ff8 CR3: 00000003ed126006 CR4: 00000000007706e0
[    4.792339] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    4.796829] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[    4.801342] PKRU: 55555554
[    4.804118] Call Trace:
[    4.806800]  ? sisevt_check_fopmap+0xb8/0xc3 [sisevt]
[    4.810487]  ? sisevt_hook_sys_openat+0x1f4/0x258 [sisevt]
[    4.814376]  ? __ia32_sys_open+0x20/0x20
[    4.817619]  ? sisevt64_sys_openat+0x1f/0x20 [sisevt]
[    4.821332]  ? do_syscall_64+0x5b/0x1a0
[    4.824576]  ? entry_SYSCALL_64_after_hwframe+0x65/0xca

• Can't collect vmcore while kdump.service is configured correctly.