From: Daniel Borkmann <dborkman@redhat.com>
To: Jesse Gross <jesse@nicira.com>
Cc: netdev <netdev@vger.kernel.org>,
"dev@openvswitch.org" <dev@openvswitch.org>
Subject: Re: [PATCH] ovs: queue_userspace_packet: bail out if nla_nest_start returns NULL
Date: Wed, 03 Jul 2013 19:13:55 +0200 [thread overview]
Message-ID: <51D45BD3.4050602@redhat.com> (raw)
In-Reply-To: <CAEP_g=84532Nh1wagsifOaBkCDk5eOUtG=RzWSv_Z+tPxzUOGg@mail.gmail.com>
On 07/03/2013 06:32 PM, Jesse Gross wrote:
> On Wed, Jul 3, 2013 at 1:49 AM, Daniel Borkmann <dborkman@redhat.com> wrote:
>> The return value of nla_nest_start() is not checked, and can be NULL,
>> which is then being dereferenced in nla_nest_end(). Add a check to
>> prevent such situations.
>>
>> Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
>> ---
>> On top of "net-next" tree.
>>
>> net/openvswitch/datapath.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/net/openvswitch/datapath.c b/net/openvswitch/datapath.c
>> index d12d6b8..51a3c66 100644
>> --- a/net/openvswitch/datapath.c
>> +++ b/net/openvswitch/datapath.c
>> @@ -427,6 +427,10 @@ static int queue_userspace_packet(struct net *net, int dp_ifindex,
>> upcall->dp_ifindex = dp_ifindex;
>>
>> nla = nla_nest_start(user_skb, OVS_PACKET_ATTR_KEY);
>> + if (unlikely(!nla)) {
>> + err = -ENOMEM;
>> + goto out;
>> + }
>
> nla_nest_start() doesn't allocate any memory, it only fails if there
> isn't enough space, so the correct error code would be -EMSGSIZE.
> However, we just calculated the correct size a few lines earlier and
> we don't double check the size anywhere else, so this doesn't make a
> lot of sense to me.
Fair enough, please drop this then.
prev parent reply other threads:[~2013-07-03 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 8:49 [PATCH] ovs: queue_userspace_packet: bail out if nla_nest_start returns NULL Daniel Borkmann
2013-07-03 16:32 ` Jesse Gross
2013-07-03 17:13 ` Daniel Borkmann [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=51D45BD3.4050602@redhat.com \
--to=dborkman@redhat.com \
--cc=dev@openvswitch.org \
--cc=jesse@nicira.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).