From: syzbot <syzbot+60a66d44892b66b56545@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, n.zhandarovich@fintech.ru,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [wpan?] KMSAN: uninit-value in ieee802154_hdr_push (2)
Date: Tue, 13 Feb 2024 06:51:03 -0800 [thread overview]
Message-ID: <000000000000fed2a7061144854c@google.com> (raw)
In-Reply-To: <20240213141308.3138-1-n.zhandarovich@fintech.ru>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KMSAN: uninit-value in ieee802154_hdr_push
=====================================================
BUG: KMSAN: uninit-value in ieee802154_hdr_push_sechdr net/ieee802154/header_ops.c:54 [inline]
BUG: KMSAN: uninit-value in ieee802154_hdr_push+0x971/0xb90 net/ieee802154/header_ops.c:108
ieee802154_hdr_push_sechdr net/ieee802154/header_ops.c:54 [inline]
ieee802154_hdr_push+0x971/0xb90 net/ieee802154/header_ops.c:108
ieee802154_header_create+0x9c0/0xc00 net/mac802154/iface.c:396
wpan_dev_hard_header include/net/cfg802154.h:524 [inline]
dgram_sendmsg+0xd1e/0x1500 net/ieee802154/socket.c:677
ieee802154_sock_sendmsg+0x96/0xd0 net/ieee802154/socket.c:96
sock_sendmsg_nosec net/socket.c:730 [inline]
__sock_sendmsg+0x30e/0x380 net/socket.c:745
____sys_sendmsg+0x877/0xb60 net/socket.c:2584
___sys_sendmsg+0x28d/0x3c0 net/socket.c:2638
__sys_sendmsg net/socket.c:2667 [inline]
__do_sys_sendmsg net/socket.c:2676 [inline]
__se_sys_sendmsg net/socket.c:2674 [inline]
__x64_sys_sendmsg+0x307/0x4a0 net/socket.c:2674
do_syscall_64+0x76/0x150
entry_SYSCALL_64_after_hwframe+0x6c/0x74
Local variable hdr created at:
ieee802154_header_create+0x4e/0xc00 net/mac802154/iface.c:360
wpan_dev_hard_header include/net/cfg802154.h:524 [inline]
dgram_sendmsg+0xd1e/0x1500 net/ieee802154/socket.c:677
CPU: 0 PID: 5449 Comm: syz-executor.0 Not tainted 6.8.0-rc4-next-20240213-syzkaller-g46d4e2eb58e1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
=====================================================
Tested on:
commit: 46d4e2eb Add linux-next specific files for 20240213
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=1553bdec180000
kernel config: https://syzkaller.appspot.com/x/.config?x=e558550134480d4a
dashboard link: https://syzkaller.appspot.com/bug?extid=60a66d44892b66b56545
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
next parent reply other threads:[~2024-02-13 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240213141308.3138-1-n.zhandarovich@fintech.ru>
2024-02-13 14:51 ` syzbot [this message]
[not found] <20251213214713.1110447-3-katharasasikumar007@gmail.com>
2025-12-13 22:51 ` [syzbot] [wpan?] KMSAN: uninit-value in ieee802154_hdr_push (2) syzbot
[not found] <20251213203625.1101692-2-katharasasikumar007@gmail.com>
2025-12-13 21:28 ` syzbot
[not found] <20240213141705.3267-1-n.zhandarovich@fintech.ru>
2024-02-13 15:18 ` syzbot
2024-01-02 13:42 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=000000000000fed2a7061144854c@google.com \
--to=syzbot+60a66d44892b66b56545@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=n.zhandarovich@fintech.ru \
--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