From: Jakub Kicinski <kuba@kernel.org>
To: Minsuk Kang <linuxlovemin@yonsei.ac.kr>
Cc: krzysztof.kozlowski@linaro.org, netdev@vger.kernel.org,
aloisio.almeida@openbossa.org, sameo@linux.intel.com,
lauro.venancio@openbossa.org, linville@tuxdriver.com,
dokyungs@yonsei.ac.kr, jisoo.jang@yonsei.ac.kr
Subject: Re: [PATCH net] nfc: pn533: Wait for out_urb's completion in pn533_usb_send_frame()
Date: Thu, 5 Jan 2023 21:26:06 -0800 [thread overview]
Message-ID: <20230105212606.2f14e5a9@kernel.org> (raw)
In-Reply-To: <20230104121711.7809-1-linuxlovemin@yonsei.ac.kr>
On Wed, 4 Jan 2023 21:17:11 +0900 Minsuk Kang wrote:
> Fix a use-after-free that occurs in hcd when in_urb sent from
> pn533_usb_send_frame() is completed earlier than out_urb. Its callback
> frees the skb data in pn533_send_async_complete() that is used as a
> transfer buffer of out_urb. Wait before sending in_urb until the
> callback of out_urb is called. To modify the callback of out_urb alone,
> separate the complete function of out_urb and ack_urb.
>
> Found by a modified version of syzkaller.
>
> BUG: KASAN: use-after-free in dummy_timer
> Call Trace:
> memcpy
> dummy_timer
> call_timer_fn
> run_timer_softirq
> __do_softirq
> irq_exit_rcu
> sysvec_apic_timer_interrupt
Could you add fine names and line numbers to the stack trace
(use scripts/decode_stacktrace.sh)? dummy_timer is a very generic
name, it'd be useful to tie it to the gadget device via file name.
> Fixes: c46ee38620a2 ("NFC: pn533: add NXP pn533 nfc device driver")
> Signed-off-by: Minsuk Kang <linuxlovemin@yonsei.ac.kr>
> ---
> drivers/nfc/pn533/usb.c | 37 ++++++++++++++++++++++++++++++++++---
> 1 file changed, 34 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/nfc/pn533/usb.c b/drivers/nfc/pn533/usb.c
> index 6f71ac72012e..325818fbaf3b 100644
> --- a/drivers/nfc/pn533/usb.c
> +++ b/drivers/nfc/pn533/usb.c
> @@ -48,6 +48,8 @@ struct pn533_usb_phy {
> struct usb_interface *interface;
>
> struct urb *out_urb;
> + struct completion *out_done;
Why keep this pointer for the lifetime of the device instead of putting
it on the stack? For inspiration please take a look at
struct pn533_acr122_poweron_rdr_arg
prev parent reply other threads:[~2023-01-06 5:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 12:17 [PATCH net] nfc: pn533: Wait for out_urb's completion in pn533_usb_send_frame() Minsuk Kang
2023-01-06 5:26 ` Jakub Kicinski [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=20230105212606.2f14e5a9@kernel.org \
--to=kuba@kernel.org \
--cc=aloisio.almeida@openbossa.org \
--cc=dokyungs@yonsei.ac.kr \
--cc=jisoo.jang@yonsei.ac.kr \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lauro.venancio@openbossa.org \
--cc=linuxlovemin@yonsei.ac.kr \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=sameo@linux.intel.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).