From: Greg KH <gregkh@linuxfoundation.org>
To: "zdi-disclosures@trendmicro.com" <zdi-disclosures@trendmicro.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"oneukum@suse.com" <oneukum@suse.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: ZDI-CAN-22166: New Vulnerability Report
Date: Sat, 30 Sep 2023 08:55:42 +0200 [thread overview]
Message-ID: <2023093035-primate-prankster-7f60@gregkh> (raw)
In-Reply-To: <DM5PR0102MB3477C75A38D67E275032FADB80C0A@DM5PR0102MB3477.prod.exchangelabs.com>
On Fri, Sep 29, 2023 at 07:00:54PM +0000, zdi-disclosures@trendmicro.com wrote:
> Trend Micro's Zero Day Initiative has identified a vulnerability affecting the following products:
> Linux - Kernel
As reported to you before, this is NOT a "vulnerability" but rather,
just a normal bug that you are somehow claiming needs to be fixed.
Patches to help resolve the issue would be most appreciated as you are
in the best position to test them.
thanks,
greg k-h
prev parent reply other threads:[~2023-09-30 6:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 19:00 ZDI-CAN-22166: New Vulnerability Report zdi-disclosures
2023-09-30 6:55 ` Greg KH [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=2023093035-primate-prankster-7f60@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=zdi-disclosures@trendmicro.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).