[syzbot] [media?] WARNING in cec_data_cancel

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 905b00721763 Merge branch 'for-next/core' into for-kernelci
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=117a5b52180000
kernel config: https://syzkaller.appspot.com/x/.config?x=c9378409372fa395
dashboard link: https://syzkaller.appspot.com/bug?extid=57d7c816f3eb3c02ffa9
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/afc82f43a122/disk-905b0072.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0b11ab3a34e1/vmlinux-905b0072.xz
kernel image: https://storage.googleapis.com/syzbot-assets/eff038048b1b/Image-905b0072.gz.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 1133 at drivers/media/cec/core/cec-adap.c:365 cec_data_cancel+0x620/0x7bc drivers/media/cec/core/cec-adap.c:365
Modules linked in:
CPU: 1 PID: 1133 Comm: syz-executor.4 Tainted: G B 6.8.0-rc4-syzkaller-g905b00721763 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : cec_data_cancel+0x620/0x7bc drivers/media/cec/core/cec-adap.c:365
lr : cec_data_cancel+0x620/0x7bc drivers/media/cec/core/cec-adap.c:365
sp : ffff800097c87730
x29: ffff800097c87740 x28: ffff0000c86cc810 x27: ffff0000c86cc800
x26: dfff800000000000 x25: 1fffe0001a08c4df x24: 0000000000000000
x23: 0000000000000040 x22: 0000000000000000 x21: ffff0000d04626f8
x20: ffff0000d0462000 x19: ffff0000c86cc800 x18: 1fffe00036804796
x17: ffff80008ec8d000 x16: ffff800080275750 x15: 0000000000000001
x14: 1ffff00012f90ea0 x13: 0000000000000000 x12: 0000000000000000
x11: 0000000000040000 x10: 00000000000008e5 x9 : ffff8000ac1bf000
x8 : 00000000000008e6 x7 : 0000000000000000 x6 : ffff800086e8a5fc
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff800080316bac
x2 : ffff0000c86cc800 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
cec_data_cancel+0x620/0x7bc drivers/media/cec/core/cec-adap.c:365
cec_transmit_msg_fh+0xfc0/0x1a74
cec_transmit drivers/media/cec/core/cec-api.c:230 [inline]
cec_ioctl+0x239c/0x37b0 drivers/media/cec/core/cec-api.c:534
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:871 [inline]
__se_sys_ioctl fs/ioctl.c:857 [inline]
__arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:857
__invoke_syscall arch/arm64/kernel/syscall.c:37 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:51
el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:136
do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:155
el0_svc+0x54/0x158 arch/arm64/kernel/entry-common.c:678
el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:696
el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598
irq event stamp: 0
hardirqs last enabled at (0): [<0000000000000000>] 0x0
hardirqs last disabled at (0): [<ffff8000801b5074>] copy_process+0x1318/0x3478 kernel/fork.c:2441
softirqs last enabled at (0): [<ffff8000801b509c>] copy_process+0x1340/0x3478 kernel/fork.c:2442
softirqs last disabled at (0): [<0000000000000000>] 0x0
---[ end trace 0000000000000000 ]---


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