From: <jim_baxter@mentor.com>
To: <linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Felipe Balbi <balbi@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mike Looijmans <mike.looijmans@topic.nl>,
Robert Baldyga <r.baldyga@samsung.com>,
Jim Baxter <jim_baxter@mentor.com>,
Mark Craske <Mark_Craske@mentor.com>
Subject: [PATCH v1 1/1] usb: gadget: NCM: NULL pointer dereference in eth_start_xmit
Date: Mon, 25 Apr 2016 16:25:03 +0100 [thread overview]
Message-ID: <1461597903-17788-1-git-send-email-jim_baxter@mentor.com> (raw)
From: Jim Baxter <jim_baxter@mentor.com>
"Unable to handle kernel NULL pointer dereference at virtual address
00000078" is reported with "PC is at eth_start_xmit+0x19c/0x378 [u_ether]"
The failure scenario is seen when closing the NCM connection while the
TCP/IPv6 stack is still trying to transmit over NCM.
Defensive code is missing from commit
6d3865f9d41f15ddbcecaa6722871fc0db21d7ab
"usb: gadget: NCM: Add transmit multi-frame."
Add check for non-NULL dev->port_usb before accessing
dev->port_usb->supports_multi_frame.
Signed-off-by: Mark Craske <Mark_Craske@mentor.com>
Signed-off-by: Jim Baxter <jim_baxter@mentor.com>
---
drivers/usb/gadget/function/u_ether.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/function/u_ether.c b/drivers/usb/gadget/function/u_ether.c
index 637809e..68f0b7b 100644
--- a/drivers/usb/gadget/function/u_ether.c
+++ b/drivers/usb/gadget/function/u_ether.c
@@ -556,7 +556,8 @@ static netdev_tx_t eth_start_xmit(struct sk_buff *skb,
/* Multi frame CDC protocols may store the frame for
* later which is not a dropped frame.
*/
- if (dev->port_usb->supports_multi_frame)
+ if (dev->port_usb &&
+ dev->port_usb->supports_multi_frame)
goto multiframe;
goto drop;
}
--
1.9.1
next reply other threads:[~2016-04-25 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 15:25 jim_baxter [this message]
2016-04-25 16:51 ` One Thousand Gnomes
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=1461597903-17788-1-git-send-email-jim_baxter@mentor.com \
--to=jim_baxter@mentor.com \
--cc=Mark_Craske@mentor.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mike.looijmans@topic.nl \
--cc=r.baldyga@samsung.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
all inboxes | Powered by JetHome®