From: "Neronin, Niklas" <niklas.neronin@linux.intel.com>
To: Jinjiang Tu <tujinjiang@huawei.com>
Cc: cve@kernel.org, gregkh@linuxfoundation.org,
linux-cve-announce@vger.kernel.org, linux-kernel@vger.kernel.org,
Mathias Nyman <mathias.nyman@linux.intel.com>
Subject: Re: CVE-2024-42226: usb: xhci: prevent potential failure in handle_tx_event() for Transfer events without TRB
Date: Wed, 7 Aug 2024 12:31:56 +0300 [thread overview]
Message-ID: <6327d2ed-f1de-406d-a713-97934dbb6c39@linux.intel.com> (raw)
In-Reply-To: <d36feb2f-c1f2-90c2-bb33-e6d0ff41096d@huawei.com>
On 06/08/2024 16.53, Jinjiang Tu wrote:
>
> 在 2024/8/6 19:15, Neronin, Niklas 写道:
>> On 06/08/2024 12.25, Jinjiang Tu wrote:
>>> Hi, Niklas
>>>
>>> The commit 66cb618bf0bb ("usb: xhci: prevent potential failure in handle_tx_event() for Transfer events without TRB")
>>> has been assigned with CVE-2024-42226, but the commit has been reverted in 6.1.99 and 6.6.39 due to
>>> performance regression. Do you have a plan to address this issue, or if this CVE should be rejected?
>>>
>>> Thanks!
>>>
>> Hi,
>>
>> Currently, I have no plan to address this issue.
>>
>> The commit in question, was not intended for any previous Linux versions.
>> It was created as part of my handle_tx_event() rework series. Future changes
>> in said series could potentially trigger the issue, so preemptively preventing
>> it was both simpler and more secure.
> I don't know if I'm understanding this right, do you mean the issue mentioned in
> the commit will not be actually triggered in previous Linux versions? Now the commit
> is reverted in v6.1 and v6.6, but the issue can not be triggered in these versions,
> so no more fixes patch is needed for these LTS versions?
I'm not aware of any cases where this issue has been triggered. As it has been in the
Linux kernel for a long time, I assume it does not trigger.
Thanks,
Niklas
next prev parent reply other threads:[~2024-08-07 9:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024073038-CVE-2024-42226-fa39@gregkh>
2024-08-05 7:01 ` CVE-2024-42226: usb: xhci: prevent potential failure in handle_tx_event() for Transfer events without TRB Jinjiang Tu
2024-08-06 9:25 ` Jinjiang Tu
2024-08-06 11:15 ` Neronin, Niklas
2024-08-06 13:53 ` Jinjiang Tu
2024-08-07 9:31 ` Neronin, Niklas [this message]
2024-08-11 15:33 ` Greg KH
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=6327d2ed-f1de-406d-a713-97934dbb6c39@linux.intel.com \
--to=niklas.neronin@linux.intel.com \
--cc=cve@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=tujinjiang@huawei.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