From: Johan Hovold <johan+linaro@kernel.org>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Krishna Kurapati <quic_kriskura@quicinc.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
linux-usb@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Johan Hovold <johan+linaro@kernel.org>
Subject: [PATCH 0/2] USB: dwc3: qcom: fix NULL-deref on suspend
Date: Wed, 7 Jun 2023 12:05:38 +0200 [thread overview]
Message-ID: <20230607100540.31045-1-johan+linaro@kernel.org> (raw)
Some dwc3 glue drivers are currently accessing the driver data of the
child core device directly, which is clearly a bad idea as the child may
not have probed yet or may have been unbound from its driver.
This series fixes some of the symptoms of these layering violations as
fixing the glue drivers properly is going to take a fair bit of work.
Johan
Johan Hovold (2):
USB: dwc3: qcom: fix NULL-deref on suspend
USB: dwc3: fix use-after-free on core driver unbind
drivers/usb/dwc3/core.c | 5 +++++
drivers/usb/dwc3/dwc3-qcom.c | 11 ++++++++++-
2 files changed, 15 insertions(+), 1 deletion(-)
--
2.39.3
next reply other threads:[~2023-06-07 11:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 10:05 Johan Hovold [this message]
2023-06-07 10:05 ` [PATCH 1/2] USB: dwc3: qcom: fix NULL-deref on suspend Johan Hovold
2023-06-08 12:49 ` Manivannan Sadhasivam
2023-06-09 0:32 ` Thinh Nguyen
2023-06-07 10:05 ` [PATCH 2/2] USB: dwc3: fix use-after-free on core driver unbind Johan Hovold
2023-06-08 13:02 ` Manivannan Sadhasivam
2023-06-08 13:09 ` Johan Hovold
2023-06-08 13:23 ` Manivannan Sadhasivam
2023-06-08 13:49 ` Johan Hovold
2023-06-08 15:16 ` Manivannan Sadhasivam
2023-06-09 0:33 ` Thinh Nguyen
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=20230607100540.31045-1-johan+linaro@kernel.org \
--to=johan+linaro@kernel.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_kriskura@quicinc.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