public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+9d34f80f841e948c3fdb@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] Re: [syzbot] [usb?] KMSAN: kernel-usb-infoleak in usbtmc_write
Date: Thu, 05 Sep 2024 01:29:39 -0700	[thread overview]
Message-ID: <00000000000071b79406215b1789@google.com> (raw)
In-Reply-To: <000000000000407108061e0ed264@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: Re: [syzbot] [usb?] KMSAN: kernel-usb-infoleak in usbtmc_write
Author: lizhi.xu@windriver.com

Short write.
User input data maybe invalid, clear the data buf of the user data before copying from user.

#syz test

diff --git a/drivers/usb/class/usbtmc.c b/drivers/usb/class/usbtmc.c
index e9ddaa9b580d..65092891ba2c 100644
--- a/drivers/usb/class/usbtmc.c
+++ b/drivers/usb/class/usbtmc.c
@@ -1586,6 +1586,8 @@ static ssize_t usbtmc_write(struct file *filp, const char __user *buf,
 		aligned = (transfersize + (USBTMC_HEADER_SIZE + 3)) & ~3;
 	}
 
+	printk("xf size: %u, count: %u, %s\n", transfersize, count, __func__);
+	memset(&buffer[USBTMC_HEADER_SIZE], 0, count);
 	if (copy_from_user(&buffer[USBTMC_HEADER_SIZE], buf, transfersize)) {
 		retval = -EFAULT;
 		up(&file_data->limit_write_sem);

      parent reply	other threads:[~2024-09-05  8:29 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25  9:14 [syzbot] [usb?] KMSAN: kernel-usb-infoleak in usbtmc_write syzbot
2024-09-04 12:00 ` syzbot
2024-09-04 12:47   ` Edward Adam Davis
2024-09-04 13:33     ` syzbot
2024-09-04 13:55   ` [PATCH] USB: usbtmc: prevent kernel-infoleak Edward Adam Davis
2024-09-04 14:09     ` Greg KH
2024-09-04 14:13       ` Greg KH
2024-09-05 13:56         ` Edward Adam Davis
2024-09-05 14:04           ` Greg KH
2024-09-05 14:16             ` Edward Adam Davis
2024-09-06 14:11               ` [PATCH V2] USB: usbtmc: prevent kernel-usb-infoleak Edward Adam Davis
2024-09-06 14:28                 ` Alan Stern
2024-09-07  2:08                   ` Edward Adam Davis
2024-09-07 14:45                     ` Alan Stern
2024-09-08  0:59                       ` Edward Adam Davis
2024-09-08  1:32                         ` Alan Stern
2024-09-08  2:01                           ` Edward Adam Davis
2024-09-08  2:20                           ` [PATCH V3] " Edward Adam Davis
2024-09-08  5:20                             ` Greg KH
2024-09-08  7:35                               ` Edward Adam Davis
2024-09-08  7:54                                 ` Greg KH
2024-09-08  8:16                                   ` Edward Adam Davis
2024-09-08  8:33                                     ` Greg KH
2024-09-08  9:17                                       ` [PATCH v4] " Edward Adam Davis
2024-09-05 11:27   ` [syzbot] [usb?] KMSAN: kernel-usb-infoleak in usbtmc_write Edward Adam Davis
2024-09-05 15:42     ` syzbot
2024-09-05 14:21   ` Edward Adam Davis
2024-09-05 16:11     ` syzbot
2024-09-06 11:55   ` Edward Adam Davis
2024-09-06 12:29     ` syzbot
2024-09-06 12:37   ` Edward Adam Davis
2024-09-06 13:07     ` syzbot
2024-09-06 13:06   ` Edward Adam Davis
2024-09-06 13:51     ` syzbot
2024-09-06 13:52   ` Edward Adam Davis
2024-09-06 16:59     ` syzbot
2024-09-05  7:11 ` [syzbot] " syzbot
2024-09-05  8:29 ` syzbot [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=00000000000071b79406215b1789@google.com \
    --to=syzbot+9d34f80f841e948c3fdb@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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