From: syzbot <syzbot+3361c2d6f78a3e0892f9@syzkaller.appspotmail.com>
To: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [usb?] KMSAN: uninit-value in mii_nway_restart (2)
Date: Mon, 17 Feb 2025 03:55:16 -0800 [thread overview]
Message-ID: <67b323a4.050a0220.173698.002a.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 128c8f96eb86 Merge tag 'drm-fixes-2025-02-14' of https://g..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=11546098580000
kernel config: https://syzkaller.appspot.com/x/.config?x=264db44f1897cdc3
dashboard link: https://syzkaller.appspot.com/bug?extid=3361c2d6f78a3e0892f9
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=17d9d9b0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1039d9b0580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7aa6f3aa12c5/disk-128c8f96.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7ca2c0dbfd2f/vmlinux-128c8f96.xz
kernel image: https://storage.googleapis.com/syzbot-assets/aa690978a38e/bzImage-128c8f96.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3361c2d6f78a3e0892f9@syzkaller.appspotmail.com
=====================================================
BUG: KMSAN: uninit-value in mii_nway_restart+0x119/0x1e0 drivers/net/mii.c:468
mii_nway_restart+0x119/0x1e0 drivers/net/mii.c:468
ch9200_bind+0x238/0xeb0 drivers/net/usb/ch9200.c:354
usbnet_probe+0xdb0/0x3eb0 drivers/net/usb/usbnet.c:1761
usb_probe_interface+0xd33/0x12e0 drivers/usb/core/driver.c:396
really_probe+0x4dc/0xd90 drivers/base/dd.c:658
__driver_probe_device+0x2ab/0x5d0 drivers/base/dd.c:800
driver_probe_device+0x72/0x890 drivers/base/dd.c:830
__device_attach_driver+0x568/0x9e0 drivers/base/dd.c:958
bus_for_each_drv+0x403/0x620 drivers/base/bus.c:462
__device_attach+0x3c1/0x650 drivers/base/dd.c:1030
device_initial_probe+0x32/0x40 drivers/base/dd.c:1079
bus_probe_device+0x3dc/0x5c0 drivers/base/bus.c:537
device_add+0x13aa/0x1ba0 drivers/base/core.c:3665
usb_set_configuration+0x31c9/0x38d0 drivers/usb/core/message.c:2210
usb_generic_driver_probe+0x109/0x2a0 drivers/usb/core/generic.c:250
usb_probe_device+0x3a7/0x690 drivers/usb/core/driver.c:291
really_probe+0x4dc/0xd90 drivers/base/dd.c:658
__driver_probe_device+0x2ab/0x5d0 drivers/base/dd.c:800
driver_probe_device+0x72/0x890 drivers/base/dd.c:830
__device_attach_driver+0x568/0x9e0 drivers/base/dd.c:958
bus_for_each_drv+0x403/0x620 drivers/base/bus.c:462
__device_attach+0x3c1/0x650 drivers/base/dd.c:1030
device_initial_probe+0x32/0x40 drivers/base/dd.c:1079
bus_probe_device+0x3dc/0x5c0 drivers/base/bus.c:537
device_add+0x13aa/0x1ba0 drivers/base/core.c:3665
usb_new_device+0x15f0/0x2470 drivers/usb/core/hub.c:2652
hub_port_connect drivers/usb/core/hub.c:5523 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5663 [inline]
port_event drivers/usb/core/hub.c:5823 [inline]
hub_event+0x4ffb/0x72d0 drivers/usb/core/hub.c:5905
process_one_work kernel/workqueue.c:3236 [inline]
process_scheduled_works+0xc1a/0x1e80 kernel/workqueue.c:3317
worker_thread+0xea7/0x14f0 kernel/workqueue.c:3398
kthread+0x6b9/0xef0 kernel/kthread.c:464
ret_from_fork+0x6d/0x90 arch/x86/kernel/process.c:148
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
Local variable buff created at:
ch9200_mdio_read+0x3c/0x100 drivers/net/usb/ch9200.c:180
mii_nway_restart+0x8a/0x1e0 drivers/net/mii.c:466
CPU: 1 UID: 0 PID: 3067 Comm: kworker/1:2 Not tainted 6.14.0-rc2-syzkaller-00185-g128c8f96eb86 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
Workqueue: usb_hub_wq hub_event
=====================================================
---
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
reply other threads:[~2025-02-17 11:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=67b323a4.050a0220.173698.002a.GAE@google.com \
--to=syzbot+3361c2d6f78a3e0892f9@syzkaller.appspotmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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;
as well as URLs for NNTP newsgroup(s).