From: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 44631] New: Missing NULL check of the return value of get_skb() in function send_flowc()
Date: Fri, 13 Jul 2012 02:16:03 +0000 (UTC) [thread overview]
Message-ID: <bug-44631-11804@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=44631
Summary: Missing NULL check of the return value of get_skb() in
function send_flowc()
Product: Drivers
Version: 2.5
Kernel Version: 2.6.39
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Infiniband/RDMA
AssignedTo: drivers_infiniband-rdma-ztI5WcYan/vQLgFONoPN62D2FQJk+8+b@public.gmane.org
ReportedBy: rucsoftsec-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Regression: No
Function get_skb() may return a NULL pointer, and its return value shall be
checked before used. But in function send_flowc() after get_skb() is called(at
drivers/infiniband/hw/cxgb4/cm.c:362), the return value is immediately used as
a parameter of __skb_put() without NULL check. Besides, there is no check
before the parameter is dereferenced in the callee function __skb_put(). So an
invalid memory access may be triggered.
The related code snippets in send_flowc() are as following.
send_flowc() @@drivers/infiniband/hw/cxgb4/cm.c:362
362 skb = get_skb(skb, flowclen, GFP_KERNEL);
363 flowc = (struct fw_flowc_wr *)__skb_put(skb, flowclen);
And the implementation of get_skb() are as following.
get_skb() drivers/infiniband/hw/cxgb4/cm.c:301
301static struct sk_buff *get_skb(struct sk_buff *skb, int len, gfp_t gfp)
302{
303 if (skb && !skb_is_nonlinear(skb) && !skb_cloned(skb)) {
304 skb_trim(skb, 0);
305 skb_get(skb);
306 skb_reset_transport_header(skb);
307 } else {
308 skb = alloc_skb(len, gfp);
309 }
310 return skb;
311}
Following is a call instance of snd_flowc.
act_establish @@drivers/infiniband/hw/cxgb4/cm.c:695
695 /* start MPA negotiation */
696 send_flowc(ep, NULL);
So from the source code we can see that potential NULL dereference fault exists
when path act_establish()->send_flowc()->get_skb()->alloc_skb() is executed.
Thank you
RUC_Soft_Sec
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2012-07-13 2:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-44631-11804@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon-590eeb7gvniway/ihj7yzeb+6bgklq7r@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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