mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Colin Ian King <colin.king@canonical.com>
To: Casey Schaufler <casey@schaufler-ca.com>,
	James Morris <james.l.morris@oracle.com>,
	"Serge E . Hally" <serge@hallyn.com>,
	linux-security-module@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][V2] Smack: fix a dereference before null check on sock->sk
Date: Thu, 9 Feb 2017 18:45:54 +0000	[thread overview]
Message-ID: <0342e3f4-9436-ab81-fa33-a5bfe55229b7@canonical.com> (raw)
In-Reply-To: <a01d151d-50ed-c778-d30f-2b9e1c8defb6@schaufler-ca.com>

On 09/02/17 18:44, Casey Schaufler wrote:
> On 2/9/2017 9:11 AM, Colin King wrote:
>> From: Colin Ian King <colin.king@canonical.com>
>>
>> The initialisation of pointer ssp is from a dereference on sock->sk
>> before sock-sk is null checked, hence there is a potential for a
>> null pointer deference.  Fix this by moving the assignment of ssp
>> to just before it is used in the call to smk_ipv6_check.
>>
>> Also minor clean up of code to reduce #ifdef noise.
>> Detected with CoverityScan, CID#1324196 ("Dereference before null check")
>>
>> Signed-off-by: Colin Ian King <colin.king@canonical.com>
>> ---
>>  security/smack/smack_lsm.c | 19 +++++++++++--------
>>  1 file changed, 11 insertions(+), 8 deletions(-)
>>
>> diff --git a/security/smack/smack_lsm.c b/security/smack/smack_lsm.c
>> index fc8fb31..0c5656d 100644
>> --- a/security/smack/smack_lsm.c
>> +++ b/security/smack/smack_lsm.c
>> @@ -2897,10 +2897,6 @@ static int smack_socket_connect(struct socket *sock, struct sockaddr *sap,
>>  #if IS_ENABLED(CONFIG_IPV6)
>>  	struct sockaddr_in6 *sip = (struct sockaddr_in6 *)sap;
>>  #endif
>> -#ifdef SMACK_IPV6_SECMARK_LABELING
>> -	struct smack_known *rsp;
>> -	struct socket_smack *ssp = sock->sk->sk_security;
>> -#endif
>>  
>>  	if (sock->sk == NULL)
>>  		return 0;
>> @@ -2915,10 +2911,17 @@ static int smack_socket_connect(struct socket *sock, struct sockaddr *sap,
>>  		if (addrlen < sizeof(struct sockaddr_in6))
>>  			return -EINVAL;
>>  #ifdef SMACK_IPV6_SECMARK_LABELING
>> -		rsp = smack_ipv6host_label(sip);
>> -		if (rsp != NULL)
>> -			rc = smk_ipv6_check(ssp->smk_out, rsp, sip,
>> -						SMK_CONNECTING);
>> +		{
>> +			struct smack_known *rsp = smack_ipv6host_label(sip);
> 
> I make a habit of not using nested declarations.
> I appreciate the intent of the patch, but I would
> rather take a more global approach to the cleanup.

Yup. tad frustrating this, the original patch is now going to turn into
a larger change set, which was not my original intent in a trivial bug fix.

> 
>> +
>> +			if (rsp != NULL) {
>> +				struct socket_smack *ssp =
>> +					sock->sk->sk_security;
>> +
>> +				rc = smk_ipv6_check(ssp->smk_out, rsp, sip,
>> +						    SMK_CONNECTING);
>> +			}
>> +		}
>>  #endif
>>  #ifdef SMACK_IPV6_PORT_LABELING
>>  		rc = smk_ipv6_port_check(sock->sk, sip, SMK_CONNECTING);
> 

      reply	other threads:[~2017-02-09 18:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09 17:11 Colin King
2017-02-09 18:44 ` Casey Schaufler
2017-02-09 18:45   ` Colin Ian King [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=0342e3f4-9436-ab81-fa33-a5bfe55229b7@canonical.com \
    --to=colin.king@canonical.com \
    --cc=casey@schaufler-ca.com \
    --cc=james.l.morris@oracle.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=serge@hallyn.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®