[Android 5.15] general protection fault in tracing_release_file_tr

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 61d896ee2a80 Revert "hdlc_ppp: sync per-proto timers befor..
git tree: android13-5.15-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=12a783b9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=43676e801f1929a9
dashboard link: https://syzkaller.appspot.com/bug?extid=e4b29fa30530aa9e3973
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10a02649580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15e25e32580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/bcb85cf50754/disk-61d896ee.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7e4ac22ab0e5/vmlinux-61d896ee.xz
kernel image: https://storage.googleapis.com/syzbot-assets/14b47a248e31/bzImage-61d896ee.xz

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

general protection fault, probably for non-canonical address 0xdffffc0000000005: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f]
CPU: 1 PID: 303 Comm: syz-executor298 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:tracing_release_file_tr+0x48/0x100 kernel/trace/trace.c:4888
Code: 81 c3 d8 02 00 00 48 89 d8 48 c1 e8 03 42 80 3c 38 00 74 08 48 89 df e8 16 0e 3c 00 48 8b 1b 48 83 c3 28 48 89 d8 48 c1 e8 03 <42> 80 3c 38 00 74 08 48 89 df e8 f9 0d 3c 00 48 8b 1b 48 85 db 74
RSP: 0018:ffffc90000987c00 EFLAGS: 00010206
RAX: 0000000000000005 RBX: 0000000000000028 RCX: ffff88810af33b40
RDX: 0000000000000000 RSI: ffff88811d3c5080 RDI: ffff888111ec8370
RBP: ffffc90000987c20 R08: ffff8881053d14c7 R09: 1ffff11020a7a298
R10: dffffc0000000000 R11: ffffed1020a7a299 R12: 1ffff11023a78a15
R13: ffff88811d3c5080 R14: ffff888111ec8370 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc38ab34230 CR3: 000000000660f000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__fput+0x22b/0x900 fs/file_table.c:311
____fput+0x15/0x20 fs/file_table.c:339
task_work_run+0x127/0x190 kernel/task_work.c:188
exit_task_work include/linux/task_work.h:33 [inline]
do_exit+0xb70/0x29a0 kernel/exit.c:890
do_group_exit+0x149/0x310 kernel/exit.c:1004
__do_sys_exit_group kernel/exit.c:1015 [inline]
__se_sys_exit_group kernel/exit.c:1013 [inline]
__x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1013
x64_sys_call+0x832/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:232
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fc38aa97405
Code: Unable to access opcode bytes at RIP 0x7fc38aa973db.
RSP: 002b:00007ffc26b6e2c8 EFLAGS: 00000206 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fc38aa97405
RDX: 00000000000000e7 RSI: ffffffffffffffd8 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 00000000000a8c88
R10: 0000000000000048 R11: 0000000000000206 R12: 0000000000000000
R13: 00007fc38ab2d110 R14: 00007fc38ab2f3a8 R15: 00007fc38ab2f3c0
</TASK>
Modules linked in:
---[ end trace 8b6775e65cd73578 ]---
RIP: 0010:tracing_release_file_tr+0x48/0x100 kernel/trace/trace.c:4888
Code: 81 c3 d8 02 00 00 48 89 d8 48 c1 e8 03 42 80 3c 38 00 74 08 48 89 df e8 16 0e 3c 00 48 8b 1b 48 83 c3 28 48 89 d8 48 c1 e8 03 <42> 80 3c 38 00 74 08 48 89 df e8 f9 0d 3c 00 48 8b 1b 48 85 db 74
RSP: 0018:ffffc90000987c00 EFLAGS: 00010206
RAX: 0000000000000005 RBX: 0000000000000028 RCX: ffff88810af33b40
RDX: 0000000000000000 RSI: ffff88811d3c5080 RDI: ffff888111ec8370
RBP: ffffc90000987c20 R08: ffff8881053d14c7 R09: 1ffff11020a7a298
R10: dffffc0000000000 R11: ffffed1020a7a299 R12: 1ffff11023a78a15
R13: ffff88811d3c5080 R14: ffff888111ec8370 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc38ab34230 CR3: 000000000660f000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 81 c3 d8 02 00 00 add $0x2d8,%ebx
6: 48 89 d8 mov %rbx,%rax
9: 48 c1 e8 03 shr $0x3,%rax
d: 42 80 3c 38 00 cmpb $0x0,(%rax,%r15,1)
12: 74 08 je 0x1c
14: 48 89 df mov %rbx,%rdi
17: e8 16 0e 3c 00 call 0x3c0e32
1c: 48 8b 1b mov (%rbx),%rbx
1f: 48 83 c3 28 add $0x28,%rbx
23: 48 89 d8 mov %rbx,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 38 00 cmpb $0x0,(%rax,%r15,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 48 89 df mov %rbx,%rdi
34: e8 f9 0d 3c 00 call 0x3c0e32
39: 48 8b 1b mov (%rbx),%rbx
3c: 48 85 db test %rbx,%rbx
3f: 74 .byte 0x74


---
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.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup