[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-id: <1834203638.139231427778581653.JavaMail.weblogic@epmlwas08d>
Date: Tue, 31 Mar 2015 05:09:43 +0000 (GMT)
From: Maninder Singh <maninder1.s@...sung.com>
To: Casey Schaufler <casey@...aufler-ca.com>,
Paul Moore <paul@...l-moore.com>,
Maninder Singh <maninder1.s@...sung.com>
Cc: "davem@...emloft.net" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Vaneet Narang <v.narang@...sung.com>,
AJEET YADAV <ajeet.y@...sung.com>
Subject: Re: Re: [Fix kernel crash in cipso_v4_sock_delattr ]
We are currently using 3.10.58 kernel and we are facing this issue for samck enabled system.
and as we can check in other APIs like netlbl_sock_getattr and netlbl_conn_setattr have this preventive check so we added this check for netlbl_sock_delattr also.
And regarding patch re-submission, actually we have run checkpatch.pl before submission(successfull) But when we submit the patch our editor changes tabs into space, we will resubmitt the patch ASAP.
Maninder Singh
------- Original Message -------
Sender : Casey Schaufler<casey@...aufler-ca.com>
Date : Mar 31, 2015 02:25 (GMT+09:00)
Title : Re: [Fix kernel crash in cipso_v4_sock_delattr ]
On 3/30/2015 4:32 AM, Paul Moore wrote:
> On Monday, March 30, 2015 11:09:00 AM Maninder Singh wrote:
>> Dear All,
>> we found One Kernel Crash issue in cipso_v4_sock_delattr :-
>> As Cipso supports only inet sockets so cipso_v4_sock_delattr will crash when
>> try to access any other socket type. cipso_v4_sock_delattr access
>> sk_inet->inet_opt which may contain not NULL but invalid address. we found
>> this issue with netlink socket.(reproducible by trinity using sendto system
>> call .)
> Hello,
>
> First, please go read the Documentation/SubmittingPatches from the kernel
> sources; your patch needs to be resubmitted and the instructions in that file
> will show you how to do it correctly next time.
>
> Second, this appears to only affect Smack based systems, yes? SELinux based
> systems should have the proper checking in place to prevent this (the checks
> are handled in the LSM).
This looks like a problem that was fixed some time ago.
The current Smack code clearly checks for this. What kernel
version are you testing against?
> That said, it probably wouldn't hurt to add the
> extra checking to netlbl_sock_delattr(). If you properly resubmit your patch
> I'll ACK it.
>
> -Paul
>
Powered by blists - more mailing lists