Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Zheng Yejian <zhengyejian1@huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <stable@vger.kernel.org>, <agross@kernel.org>,
	<bjorn.andersson@linaro.org>, <balbi@kernel.org>,
	<lee.jones@linaro.org>, <linux-arm-msm@vger.kernel.org>,
	<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5.15] usb: dwc3: dwc3-qcom: Add missing platform_device_put() in dwc3_qcom_acpi_register_core
Date: Mon, 6 Mar 2023 15:24:07 +0800	[thread overview]
Message-ID: <c0bc32ca-312f-d699-d19b-f4436c286dc7@huawei.com> (raw)
In-Reply-To: <ZAV+9ToKbIPFKJIs@kroah.com>

On 2023/3/6 13:49, Greg KH wrote:
> On Mon, Mar 06, 2023 at 09:26:31AM +0800, Zheng Yejian wrote:
>> On 2023/3/3 23:49, Greg KH wrote:
>>> On Fri, Mar 03, 2023 at 10:34:39AM +0800, Zheng Yejian wrote:
>>>> From: Miaoqian Lin <linmq006@gmail.com>
>>>>
>>>> commit fa0ef93868a6062babe1144df2807a8b1d4924d2 upstream.
>>>>
>>>> Add the missing platform_device_put() before return from
>>>> dwc3_qcom_acpi_register_core in the error handling case.
>>>>
>>>> Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
>>>> Link: https://lore.kernel.org/r/20211231113641.31474-1-linmq006@gmail.com
>>>> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>>>> CVE: CVE-2023-22995
>>>
>>> That is a bogus CVE, please go revoke it.
>>
>> Agree. I see this CVE and its fixes information from NVD,
>> so try to backport this patch to fix it:
>> Link: https://nvd.nist.gov/vuln/detail/CVE-2023-22995
> 
> Again, this is not a valid bug, the "problem" described can not ever be
> hit in a real system from what I can tell.

Agreed!

> 
>> Then should I just remove the "CVE: " field and send a v2 patch?
>> Or you mean "revoke" the CVE from NVD? I actually don't know how
>> to do that :(
> 
> If you care about CVEs being "real", yes, please get it revoked from the
> NVD.  There is no need to backport it either from what I can determine.
> 

Thanks for you pationce :)

--
Zheng Yejian

> thanks,
> 
> greg k-h

      reply	other threads:[~2023-03-06  7:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03  2:34 [PATCH 5.15] usb: dwc3: dwc3-qcom: Add missing platform_device_put() in dwc3_qcom_acpi_register_core Zheng Yejian
2023-03-03 15:49 ` Greg KH
2023-03-06  1:26   ` Zheng Yejian
2023-03-06  5:49     ` Greg KH
2023-03-06  7:24       ` Zheng Yejian [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=c0bc32ca-312f-d699-d19b-f4436c286dc7@huawei.com \
    --to=zhengyejian1@huawei.com \
    --cc=agross@kernel.org \
    --cc=balbi@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stable@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