From: Paul Moore <pmoore@redhat.com>
To: netdev@vger.kernel.org
Subject: Re: [PATCH] cipso: don't follow a NULL pointer when setsockopt() is called
Date: Tue, 17 Jul 2012 17:24:50 -0400 [thread overview]
Message-ID: <16005876.GSA3ToWriD@sifl> (raw)
In-Reply-To: <20120717210738.22790.23522.stgit@sifl>
On Tuesday, July 17, 2012 05:07:47 PM Paul Moore wrote:
> As reported by Alan Cox, and verified by Lin Ming, when a user
> attempts to add a CIPSO option to a socket using the CIPSO_V4_TAG_LOCAL
> tag the kernel dies a terrible death when it attempts to follow a NULL
> pointer (the skb argument to cipso_v4_validate() is NULL when called via
> the setsockopt() syscall).
>
> This patch fixes this by first checking to ensure that the skb is
> non-NULL before using it to find the incoming network interface. In
> the unlikely case where the skb is NULL and the user attempts to add
> a CIPSO option with the _TAG_LOCAL tag we return an error as this is
> not something we want to allow.
...
> CC: Lin Ming <mlin@ss.pku.edu.cn>
> Reported-by: Alan Cox <alan@lxorguk.ukuu.org.uk>
> Signed-off-by: Paul Moore <pmoore@redhat.com>
Argh, I just realized I forgot to CC the stable folks.
David, if you don't queue this up for them, let me know and I'll resend it to
stable once it hits Linus' tree.
> ---
> net/ipv4/cipso_ipv4.c | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/net/ipv4/cipso_ipv4.c b/net/ipv4/cipso_ipv4.c
> index c48adc5..667c1d4 100644
> --- a/net/ipv4/cipso_ipv4.c
> +++ b/net/ipv4/cipso_ipv4.c
> @@ -1725,8 +1725,10 @@ int cipso_v4_validate(const struct sk_buff *skb,
> unsigned char **option) case CIPSO_V4_TAG_LOCAL:
> /* This is a non-standard tag that we only allow for
> * local connections, so if the incoming interface is
> - * not the loopback device drop the packet. */
> - if (!(skb->dev->flags & IFF_LOOPBACK)) {
> + * not the loopback device drop the packet. Further,
> + * there is no legitimate reason for setting this from
> + * userspace so reject it if skb is NULL. */
> + if (skb == NULL || !(skb->dev->flags & IFF_LOOPBACK)) {
> err_offset = opt_iter;
> goto validate_return_locked;
> }
--
paul moore
security and virtualization @ redhat
next prev parent reply other threads:[~2012-07-17 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 21:07 [PATCH] cipso: don't follow a NULL pointer when setsockopt() is called Paul Moore
2012-07-17 21:24 ` Paul Moore [this message]
2012-07-17 21:31 ` David Miller
2012-07-18 13:03 ` Paul Moore
2012-07-18 16:02 ` David Miller
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=16005876.GSA3ToWriD@sifl \
--to=pmoore@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.