From: syzbot <syzbot+6e76aa21aaf2d8be6034@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [batman?] [bluetooth?] memory leak in skb_clone (3)
Date: Thu, 08 Jan 2026 18:58:01 -0800 [thread overview]
Message-ID: <69606eb9.050a0220.1c677c.03ae.GAE@google.com> (raw)
In-Reply-To: <20260109015342.306359-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
memory leak in skb_clone
2026/01/09 02:57:04 executed programs: 5
BUG: memory leak
unreferenced object 0xffff88810decb900 (size 240):
comm "kworker/u9:1", pid 5134, jiffies 4294946665
hex dump (first 32 bytes):
90 6c 45 14 81 88 ff ff 90 6c 45 14 81 88 ff ff .lE......lE.....
00 00 00 00 00 00 00 00 00 6c 45 14 81 88 ff ff .........lE.....
backtrace (crc 8f01ee2f):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4958 [inline]
slab_alloc_node mm/slub.c:5263 [inline]
kmem_cache_alloc_noprof+0x3b4/0x590 mm/slub.c:5270
skb_clone+0xae/0x2b0 net/core/skbuff.c:2087
__skb_tstamp_tx+0x3a0/0x4c0 net/core/skbuff.c:5679
hci_conn_tx_queue+0x11c/0x1d0 net/bluetooth/hci_conn.c:3050
hci_send_conn_frame net/bluetooth/hci_core.c:3086 [inline]
hci_sched_acl_pkt net/bluetooth/hci_core.c:3701 [inline]
hci_sched_acl net/bluetooth/hci_core.c:3726 [inline]
hci_tx_work+0x437/0x570 net/bluetooth/hci_core.c:3820
process_one_work+0x26b/0x620 kernel/workqueue.c:3257
process_scheduled_works kernel/workqueue.c:3340 [inline]
worker_thread+0x2c4/0x4f0 kernel/workqueue.c:3421
kthread+0x15b/0x310 kernel/kthread.c:463
ret_from_fork+0x2cf/0x300 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246
connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF
Tested on:
commit: 5572ad8f Merge tag 'trace-v6.19-rc4' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10b65f92580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d60836e327fd6756
dashboard link: https://syzkaller.appspot.com/bug?extid=6e76aa21aaf2d8be6034
compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1007119a580000
next parent reply other threads:[~2026-01-09 2:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260109015342.306359-1-kartikey406@gmail.com>
2026-01-09 2:58 ` syzbot [this message]
[not found] <20260108085646.302054-1-kartikey406@gmail.com>
2026-01-08 9:13 ` syzbot
[not found] <20260108083151.301101-1-kartikey406@gmail.com>
2026-01-08 8:51 ` syzbot
2026-01-07 17:34 syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69606eb9.050a0220.1c677c.03ae.GAE@google.com \
--to=syzbot+6e76aa21aaf2d8be6034@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®