From: patchwork-bot+netdevbpf@kernel.org
To: Shigeru Yoshida <syoshida@redhat.com>
Cc: steve.glendinning@shawell.net, UNGLinuxDriver@microchip.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+c74c24b43c9ae534f0e0@syzkaller.appspotmail.com,
syzbot+2c97a98a5ba9ea9c23bd@syzkaller.appspotmail.com
Subject: Re: [PATCH net] net: usb: smsc95xx: Fix uninit-value access in smsc95xx_read_reg
Date: Sun, 22 Oct 2023 10:40:23 +0000 [thread overview]
Message-ID: <169797122372.373.6344765542608925929.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231020170344.2450248-1-syoshida@redhat.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Sat, 21 Oct 2023 02:03:44 +0900 you wrote:
> syzbot reported the following uninit-value access issue [1]:
>
> smsc95xx 1-1:0.0 (unnamed net_device) (uninitialized): Failed to read reg index 0x00000030: -32
> smsc95xx 1-1:0.0 (unnamed net_device) (uninitialized): Error reading E2P_CMD
> =====================================================
> BUG: KMSAN: uninit-value in smsc95xx_reset+0x409/0x25f0 drivers/net/usb/smsc95xx.c:896
> smsc95xx_reset+0x409/0x25f0 drivers/net/usb/smsc95xx.c:896
> smsc95xx_bind+0x9bc/0x22e0 drivers/net/usb/smsc95xx.c:1131
> usbnet_probe+0x100b/0x4060 drivers/net/usb/usbnet.c:1750
> usb_probe_interface+0xc75/0x1210 drivers/usb/core/driver.c:396
> really_probe+0x506/0xf40 drivers/base/dd.c:658
> __driver_probe_device+0x2a7/0x5d0 drivers/base/dd.c:800
> driver_probe_device+0x72/0x7b0 drivers/base/dd.c:830
> __device_attach_driver+0x55a/0x8f0 drivers/base/dd.c:958
> bus_for_each_drv+0x3ff/0x620 drivers/base/bus.c:457
> __device_attach+0x3bd/0x640 drivers/base/dd.c:1030
> device_initial_probe+0x32/0x40 drivers/base/dd.c:1079
> bus_probe_device+0x3d8/0x5a0 drivers/base/bus.c:532
> device_add+0x16ae/0x1f20 drivers/base/core.c:3622
> usb_set_configuration+0x31c9/0x38c0 drivers/usb/core/message.c:2207
> usb_generic_driver_probe+0x109/0x2a0 drivers/usb/core/generic.c:238
> usb_probe_device+0x290/0x4a0 drivers/usb/core/driver.c:293
> really_probe+0x506/0xf40 drivers/base/dd.c:658
> __driver_probe_device+0x2a7/0x5d0 drivers/base/dd.c:800
> driver_probe_device+0x72/0x7b0 drivers/base/dd.c:830
> __device_attach_driver+0x55a/0x8f0 drivers/base/dd.c:958
> bus_for_each_drv+0x3ff/0x620 drivers/base/bus.c:457
> __device_attach+0x3bd/0x640 drivers/base/dd.c:1030
> device_initial_probe+0x32/0x40 drivers/base/dd.c:1079
> bus_probe_device+0x3d8/0x5a0 drivers/base/bus.c:532
> device_add+0x16ae/0x1f20 drivers/base/core.c:3622
> usb_new_device+0x15f6/0x22f0 drivers/usb/core/hub.c:2589
> hub_port_connect drivers/usb/core/hub.c:5440 [inline]
> hub_port_connect_change drivers/usb/core/hub.c:5580 [inline]
> port_event drivers/usb/core/hub.c:5740 [inline]
> hub_event+0x53bc/0x7290 drivers/usb/core/hub.c:5822
> process_one_work kernel/workqueue.c:2630 [inline]
> process_scheduled_works+0x104e/0x1e70 kernel/workqueue.c:2703
> worker_thread+0xf45/0x1490 kernel/workqueue.c:2784
> kthread+0x3e8/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:304
>
> [...]
Here is the summary with links:
- [net] net: usb: smsc95xx: Fix uninit-value access in smsc95xx_read_reg
https://git.kernel.org/netdev/net/c/51a32e828109
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-10-22 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 17:03 [PATCH net] net: usb: smsc95xx: Fix uninit-value access in smsc95xx_read_reg Shigeru Yoshida
2023-10-22 10:40 ` patchwork-bot+netdevbpf [this message]
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=169797122372.373.6344765542608925929.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--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=steve.glendinning@shawell.net \
--cc=syoshida@redhat.com \
--cc=syzbot+2c97a98a5ba9ea9c23bd@syzkaller.appspotmail.com \
--cc=syzbot+c74c24b43c9ae534f0e0@syzkaller.appspotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.