From: Jeongjun Park <aha310510@gmail.com>
To: syzbot+b8080cbc8d286a5fa23a@syzkaller.appspotmail.com
Cc: syzkaller-bugs@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [syzbot] [usb?] KMSAN: kernel-infoleak in iowarrior_read
Date: Thu, 12 Sep 2024 23:21:45 +0900 [thread overview]
Message-ID: <20240912142145.8418-1-aha310510@gmail.com> (raw)
In-Reply-To: <0000000000001fdbd80621e28ae3@google.com>
#syz test git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
---
drivers/usb/misc/iowarrior.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/misc/iowarrior.c b/drivers/usb/misc/iowarrior.c
index 6d28467ce352..9b5acb312a02 100644
--- a/drivers/usb/misc/iowarrior.c
+++ b/drivers/usb/misc/iowarrior.c
@@ -833,7 +833,7 @@ static int iowarrior_probe(struct usb_interface *interface,
dev->int_in_endpoint->bInterval);
/* create an internal buffer for interrupt data from the device */
dev->read_queue =
- kmalloc_array(dev->report_size + 1, MAX_INTERRUPT_BUFFER,
+ kcalloc(dev->report_size + 1, MAX_INTERRUPT_BUFFER,
GFP_KERNEL);
if (!dev->read_queue)
goto error;
--
next prev parent reply other threads:[~2024-09-12 14:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 2:05 [syzbot] [usb?] KMSAN: kernel-infoleak in iowarrior_read syzbot
2024-09-12 14:16 ` [syzbot] " syzbot
2024-09-12 14:21 ` Jeongjun Park [this message]
2024-09-12 15:47 ` syzbot
2024-09-12 18:47 ` [syzbot] " syzbot
2024-09-14 20:31 ` [syzbot] [usb?] " Jeongjun Park
2024-09-15 1:54 ` syzbot
2024-09-14 20:32 ` Jeongjun Park
2024-09-15 2:09 ` syzbot
2024-09-15 18:13 ` Jeongjun Park
2024-09-15 18:41 ` syzbot
2024-09-15 18:19 ` Jeongjun Park
2024-09-15 19:05 ` syzbot
[not found] <20240912141621.7782-1-aha310510@gmail.com>
2024-09-12 15:19 ` syzbot
[not found] <20240912184649.92658-1-djahchankoike@gmail.com>
2024-09-12 19:39 ` 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=20240912142145.8418-1-aha310510@gmail.com \
--to=aha310510@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+b8080cbc8d286a5fa23a@syzkaller.appspotmail.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