From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oo1-f80.google.com (mail-oo1-f80.google.com [209.85.161.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B461019C566 for ; Sun, 26 Apr 2026 00:22:39 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.161.80 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777162961; cv=none; b=W9kkk5B8e0CCPgbGjOfOFaowLnkglUPreN4TONANudqPhoBY5J/4dYR025MFBmdxjA4bZN5/3Vgj9MjEXCOyhIDZsJhMRvVNzMY9bu3G/PdMlF0ZKtbenXQPm5cuhibI9MyYTIbT4RZBh5gs19IR0/udt7pPh9+Dpqlr+0BDWdY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777162961; c=relaxed/simple; bh=WC0yS2RjY0llA/JyoM//jDlmFlQgInuDDBg8QRl+beI=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=bI3ejNXuLKy0vwedb7nmeHwHt7hOu+oHkCxI/v4bHBQQq5JRCXtK7Zphl7+JPBNxKJrbFE8ducXwbdlkYKDN/1PN+PN38xjPi1OqJwYW9goRSnlTGdqZ9QqCgM65Sk0kWj0uPcGpTI+9+feNaQnUgkDeHfpd1TV+HYR7Jfs3Vhs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.161.80 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oo1-f80.google.com with SMTP id 006d021491bc7-69491bd267fso11927562eaf.0 for ; Sat, 25 Apr 2026 17:22:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1777162958; x=1777767758; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Tgb+pnNi01+0iTdNJ76I2ejbdSo1gSLQ+9z5prEdm44=; b=gSRxnT1hnbE5A89og7e3UnWtvWVPUwMgjnjUh/hFLV7yFQJzaDeh5Q4TDS/2U30re7 fN1eyUevOst117uzuAlpKVs/2d0Q4VRBdiA1ogT5O5qbUJ9WTcgAmG8nVJbk4R32AiWl t5Hi3RZkAkrl1NS9Lm2sYQ0Hxx7B+PzcL9/6ku3WJsmYOz/m1xHpjNOiUaBozauDfrOO sNHx9TUGK7u8wipArWD+tG2g6Y5XP6RRDFd1Ll1v1MakNidleP1RqfHEwV/9Utyv7f70 8idDu0dmEuCz9KO3uUcEfbaL8HVHDqAJy1aJqNsGsecLUbuM0K4uMrtQmEz31N6nlNjN e42A== X-Gm-Message-State: AOJu0YyUl0Ns/6ssFUccP80qSTmAKOgvzQLlPqfdEZzec/kUlo+rLkV/ 6oVM6e8jzn6mN8zrNdAJ2r9kIeiBU1sPoHZrb87BDk5sggIfbcDjqMV3WhVrmGv9Z0efLlKzRbJ xIrRcm5bq5I0teKccngh1R61Bx2KVgkLMDYA031H92u9gK5qheHwjTHFkb+PrAA== Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6820:829:b0:696:2264:e1 with SMTP id 006d021491bc7-69622640544mr5921020eaf.25.1777162958710; Sat, 25 Apr 2026 17:22:38 -0700 (PDT) Date: Sat, 25 Apr 2026 17:22:38 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69ed5ace.170a0220.11de9.000b.GAE@google.com> Subject: [syzbot] [media?] memory leak in dvb_dmxdev_add_pid From: syzbot To: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, mchehab@kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: 27d128c1cff6 Merge tag 'trace-ring-buffer-v7.1-3' of git:/.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=126522ce580000 kernel config: https://syzkaller.appspot.com/x/.config?x=9645c21cfd1d3e8f dashboard link: https://syzkaller.appspot.com/bug?extid=ba83b7db8e644b8b7c19 compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=108352d2580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=166522ce580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/7aa00f1165c2/disk-27d128c1.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/bba58839d563/vmlinux-27d128c1.xz kernel image: https://storage.googleapis.com/syzbot-assets/6b9d69ada8d6/bzImage-27d128c1.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+ba83b7db8e644b8b7c19@syzkaller.appspotmail.com BUG: memory leak unreferenced object 0xffff88810b771800 (size 32): comm "syz.0.17", pid 5923, jiffies 4294942824 hex dump (first 32 bytes): 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 08 00 56 05 00 c9 ff ff 08 00 56 05 00 c9 ff ff ..V.......V..... backtrace (crc 1a56a8d7): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4574 [inline] slab_alloc_node mm/slub.c:4898 [inline] __kmalloc_cache_noprof+0x371/0x480 mm/slub.c:5410 kmalloc_noprof include/linux/slab.h:950 [inline] kzalloc_noprof include/linux/slab.h:1188 [inline] dvb_dmxdev_add_pid+0x9c/0x160 drivers/media/dvb-core/dmxdev.c:897 dvb_dmxdev_pes_filter_set drivers/media/dvb-core/dmxdev.c:972 [inline] dvb_demux_do_ioctl+0x3c6/0x7d0 drivers/media/dvb-core/dmxdev.c:1092 dvb_usercopy+0x116/0x2d0 drivers/media/dvb-core/dvbdev.c:996 dvb_demux_ioctl+0x29/0x40 drivers/media/dvb-core/dmxdev.c:1201 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0xf4/0x140 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xee/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f BUG: memory leak unreferenced object 0xffff8881297f65e0 (size 32): comm "syz.0.18", pid 5934, jiffies 4294942829 hex dump (first 32 bytes): 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 08 00 56 05 00 c9 ff ff 08 00 56 05 00 c9 ff ff ..V.......V..... backtrace (crc 1a56a8d7): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4574 [inline] slab_alloc_node mm/slub.c:4898 [inline] __kmalloc_cache_noprof+0x371/0x480 mm/slub.c:5410 kmalloc_noprof include/linux/slab.h:950 [inline] kzalloc_noprof include/linux/slab.h:1188 [inline] dvb_dmxdev_add_pid+0x9c/0x160 drivers/media/dvb-core/dmxdev.c:897 dvb_dmxdev_pes_filter_set drivers/media/dvb-core/dmxdev.c:972 [inline] dvb_demux_do_ioctl+0x3c6/0x7d0 drivers/media/dvb-core/dmxdev.c:1092 dvb_usercopy+0x116/0x2d0 drivers/media/dvb-core/dvbdev.c:996 dvb_demux_ioctl+0x29/0x40 drivers/media/dvb-core/dmxdev.c:1201 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0xf4/0x140 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xee/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF --- 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 syzkaller@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