From: syzbot <syzbot+d7b4dc6cd50410152534@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com,
krzysztof.kozlowski@linaro.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [net?] [nfc?] KMSAN: uninit-value in nci_rx_work
Date: Mon, 01 Jan 2024 05:38:24 -0800 [thread overview]
Message-ID: <00000000000003b4af060de27f6b@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 861deac3b092 Linux 6.7-rc7
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=136a5231e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=e0c7078a6b901aa3
dashboard link: https://syzkaller.appspot.com/bug?extid=d7b4dc6cd50410152534
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=111729e9e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1018379ee80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0ea60ee8ed32/disk-861deac3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6d69fdc33021/vmlinux-861deac3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f0158750d452/bzImage-861deac3.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d7b4dc6cd50410152534@syzkaller.appspotmail.com
=====================================================
BUG: KMSAN: uninit-value in nci_rx_work+0x2e6/0x500 net/nfc/nci/core.c:1516
nci_rx_work+0x2e6/0x500 net/nfc/nci/core.c:1516
process_one_work kernel/workqueue.c:2627 [inline]
process_scheduled_works+0x104e/0x1e70 kernel/workqueue.c:2700
worker_thread+0xf45/0x1490 kernel/workqueue.c:2781
kthread+0x3ed/0x540 kernel/kthread.c:388
ret_from_fork+0x66/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242
Uninit was created at:
slab_post_alloc_hook+0x129/0xa70 mm/slab.h:768
slab_alloc_node mm/slub.c:3478 [inline]
kmem_cache_alloc_node+0x5e9/0xb10 mm/slub.c:3523
kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:560
__alloc_skb+0x318/0x740 net/core/skbuff.c:651
alloc_skb include/linux/skbuff.h:1286 [inline]
virtual_ncidev_write+0x6d/0x280 drivers/nfc/virtual_ncidev.c:120
vfs_write+0x561/0x1490 fs/read_write.c:582
ksys_write+0x20f/0x4c0 fs/read_write.c:637
__do_sys_write fs/read_write.c:649 [inline]
__se_sys_write fs/read_write.c:646 [inline]
__x64_sys_write+0x93/0xd0 fs/read_write.c:646
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b
CPU: 0 PID: 743 Comm: kworker/u4:5 Not tainted 6.7.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Workqueue: nfc2_nci_rx_wq nci_rx_work
=====================================================
---
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
next reply other threads:[~2024-01-01 13:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 13:38 syzbot [this message]
2024-04-05 7:11 ` [syzbot] [PATCH net] nfc: nci: Fix uninit-value in nci_rx_work syzbot
2024-04-05 15:28 ` syzbot
2024-04-05 15:46 ` syzbot
2024-04-05 15:50 ` syzbot
2024-04-25 2:55 ` [syzbot] [PATCH net v2] " syzbot
2024-04-25 2:55 ` syzbot
2024-05-01 18:00 ` [syzbot] [PATCH net v3] " syzbot
2024-05-02 5:26 ` syzbot
2024-05-08 15:08 ` [syzbot] [PATCH net v4] " syzbot
2024-05-08 15:16 ` syzbot
2024-05-09 0:49 ` syzbot
2024-05-09 0:51 ` syzbot
2024-05-09 4:07 ` syzbot
2024-05-19 5:02 ` [syzbot] [PATCH net v5] " syzbot
2024-05-19 6:42 ` syzbot
2024-05-19 8:39 ` syzbot
[not found] <Zg-kEEJq2P4ic_LN@zeus>
2024-04-05 15:27 ` [syzbot] [net?] [nfc?] KMSAN: " syzbot
[not found] <ZhAYgzZva7_u08lT@zeus>
2024-04-06 14:09 ` syzbot
[not found] <ZhAc4cxnkBm003Kf@zeus>
2024-04-06 14:35 ` syzbot
[not found] <ZhAd06NiYTRbsnWv@zeus>
2024-04-06 14:50 ` syzbot
[not found] <ZinGFTKFFK1f3fvl@zeus>
2024-04-25 5:30 ` syzbot
[not found] <ZjKDQp4mfBSYpfFj@zeus>
2024-05-01 18:36 ` syzbot
[not found] <ZjMkFLuOdNVQVCl6@zeus>
2024-05-02 6:04 ` syzbot
[not found] <ZjuVaxrV8P7pUpva@zeus>
2024-05-08 21:51 ` syzbot
[not found] <ZjuXMtWceCuembsw@zeus>
2024-05-08 21:51 ` syzbot
[not found] <ZjwdgZftuDnkXa9Y@zeus>
2024-05-09 1:17 ` syzbot
[not found] <ZjweBJTpThEQSw4u@zeus>
2024-05-09 1:45 ` syzbot
[not found] <ZjxMF3ra7joqiJY2@zeus>
2024-05-09 4:38 ` syzbot
[not found] <ZkmH5ZWG2Zq7rTGc@zeus>
2024-05-19 6:17 ` syzbot
[not found] <ZkmfWXLoU21OdLcw@zeus>
2024-05-19 7:06 ` syzbot
[not found] <Zkm6qnUh6Xe2gv6-@zeus>
2024-05-19 9:11 ` 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=00000000000003b4af060de27f6b@google.com \
--to=syzbot+d7b4dc6cd50410152534@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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