BUG: unable to handle kernel NULL pointer dereference in corrupted

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 623a7e96 ANDROID: GKI: remove filp_open/close symbols from..
git tree: android12-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=148c6adf500000
kernel config: https://syzkaller.appspot.com/x/.config?x=6b3d67ba6cfe7d72
dashboard link: https://syzkaller.appspot.com/bug?extid=59eb3e7dfa79860df27c
compiler: Android (6032204 based on r370808) clang version 10.0.1 (https://android.googlesource.com/toolchain/llvm-project 6e765c10313d15c02ab29977a82938f66742c3a9)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11bde937500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10734ef3500000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+59eb3e...@syzkaller.appspotmail.com

in 30s) [K[ [0;31m* [0;1;31m* [0m] A start job is running for dev-ttyS0.device (20s / 1min 30s)[ 27.494090][ T22] audit: type=1400 audit(1607369646.036:8): avc: denied { execmem } for pid=362 comm="syz-executor001" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=1
[K[ [0;31m* [0m] A start job is running for dev-ttyS0.device (20s / 1min 30s) [K[ [0;31m* [0;1;31m* [0m] A start job is running for dev-ttyS0.device (21s / 1min 30s) [K[ [0;31m* [0;1;31m* [0m [0;31m* [0m] A start job is running for dev-ttyS0.device (21s / 1min 30s) [K[ [0;31m* [0;1;31m* [0m [0;31m* [0m] A start job is running for dev-ttyS0.device (22s / 1min 30s) [K[ [0;31m* [0;1;31m* [0m [0;31m* [0m] A start job is running for dev-ttyS0.device (22s / 1min 30s)[ 29.831640][ T691] BUG: kernel NULL pointer dereference, address: 0000000000000086


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches