From: Greg KH <gregkh@linuxfoundation.org>
To: Sabyrzhan Tasbolatov <snovitoll@gmail.com>
Cc: Oliver Neukum <oneukum@suse.com>,
syzbot+9760fbbd535cee131f81@syzkaller.appspotmail.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] usb/cdc-wdm: fix memory leak of wdm_device
Date: Mon, 11 Nov 2024 12:46:06 +0100 [thread overview]
Message-ID: <2024111145-stoop-blot-a740@gregkh> (raw)
In-Reply-To: <CACzwLxjD0PceaD27Ya6fFxKnSQZajtG2sEArqX6toS8SjNcinw@mail.gmail.com>
On Mon, Nov 11, 2024 at 03:40:29PM +0500, Sabyrzhan Tasbolatov wrote:
> On Mon, Nov 11, 2024 at 2:44 PM Oliver Neukum <oneukum@suse.com> wrote:
> I also wanted to request a CVE for my CV
> after the fix is released per kernel.org CNA rules :) but it's not so important.
Should not be a problem, but has nothing to do with this fix at the
moment :)
thanks,
greg k-h
next prev parent reply other threads:[~2024-11-11 11:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 22:48 [syzbot] [usb?] KMSAN: kernel-infoleak in wdm_read syzbot
2024-11-09 15:28 ` [PATCH] usb/cdc-wdm: fix memory leak of wdm_device Sabyrzhan Tasbolatov
2024-11-10 7:07 ` Greg KH
2024-11-10 8:21 ` [PATCH v2] usb/cdc-wdm: fix memory info leak in wdm_read Sabyrzhan Tasbolatov
2024-11-11 9:44 ` [PATCH] usb/cdc-wdm: fix memory leak of wdm_device Oliver Neukum
2024-11-11 10:40 ` Sabyrzhan Tasbolatov
2024-11-11 11:46 ` Greg KH [this message]
2024-11-11 12:01 ` [PATCH v3] usb/cdc-wdm: fix memory info leak in wdm_read Sabyrzhan Tasbolatov
2024-11-12 11:13 ` Greg KH
2024-11-12 13:29 ` [PATCH v4] " Sabyrzhan Tasbolatov
2024-11-12 15:52 ` Alan Stern
2024-11-12 19:30 ` Sabyrzhan Tasbolatov
2024-11-12 20:25 ` Alan Stern
2024-11-14 5:58 ` Sabyrzhan Tasbolatov
2024-11-11 14:29 ` [PATCH] usb/cdc-wdm: fix memory leak of wdm_device Alan Stern
2024-11-12 9:34 ` Sabyrzhan Tasbolatov
2024-11-12 15:38 ` Alan Stern
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=2024111145-stoop-blot-a740@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=snovitoll@gmail.com \
--cc=syzbot+9760fbbd535cee131f81@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;
as well as URLs for NNTP newsgroup(s).