selinux: Fix a panic in selinux_netlbl_inode_permission()
PATCH 1/1 selinux: Fix a panic in selinux_netlbl_inode_permission()
Rick McNeal from LSI identified a panic in selinux_netlbl_inode_permission() caused by a certain sequence of SUNRPC operations. The problem appears to be due to the lack of NULL pointer checking in the function; this patch adds the pointer checks so the function will exit safely in the cases where the socket is not completely initialized.
---
security/selinux/netlabel.c | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-)
security/selinux/netlabel.c +3 -2
@@ -386,11 +386,12 @@ int selinux_netlbl_inode_permission(struct inode *inode, int mask)if (!S_ISSOCK (inode->i_mode) || ((mask & (MAY_WRITE |MAY_APPEND )) ==0 ))return 0 ; - sock =SOCKET_I (inode); sk = sock->sk; +if (sk ==NULL ) +return 0 ; sksec = sk->sk_security; -if (sksec->nlbl_state !=NLBL_REQUIRE ) +if (sksec ==NULL || sksec->nlbl_state !=NLBL_REQUIRE )return 0 ;local_bh_disable ();
--
This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.
Quoted 7 lines · Paul Moore
Rick McNeal from LSI identified a panic in
selinux_netlbl_inode_permission()caused by a certain sequence of SUNRPC operations. The problem appears to be due to the lack of NULL pointer checking in the function; this patch adds the pointer checks so the function will exit safely in the cases where the socket is not completely initialized.From which kernel does this happen? Does it happen for the standard
configuration when SELinux is enabled?
Quoted 33 lines
Signed-off-by Paul Moore <[email protected]>---
security/selinux/netlabel.c | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-)security/selinux/netlabel.c +3
-3@@ -386,11 +386,12 @@ int selinux_netlbl_inode_permission(struct inode *inode, int mask)if (!S_ISSOCK (inode->i_mode) || ((mask & (MAY_WRITE |MAY_APPEND )) ==0 ))return 0 ; - sock =SOCKET_I (inode); sk = sock->sk; +if (sk ==NULL ) +return 0 ; sksec = sk->sk_security; -if (sksec->nlbl_state !=NLBL_REQUIRE ) +if (sksec ==NULL || sksec->nlbl_state !=NLBL_REQUIRE )return 0 ;local_bh_disable (); --This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.
Signature · 7 lines
James Morris <[email protected]> -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.
Quoted 9 lines · James Morris
Quoted 6 lines · Paul Moore
Rick McNeal from LSI identified a panic in
selinux_netlbl_inode_permission()caused by a certain sequence of SUNRPC operations. The problem appears to be due to the lack of NULL pointer checking in the function; this patch adds the pointer checks so the function will exit safely in the cases where the socket is not completely initialized.From which kernel does this happen?
I suspect it started back when NetLabel was included back in 2.6.19 but I need to checking everything ... I'm working on that now.
Quoted 1 line
Does it happen for the standard configuration when SELinux is enabled?
I believe so, but Rick is the expert here, I'll defer you to his email.
Quoted 31 lines
Quoted 31 lines
Signed-off-by Paul Moore <[email protected]>---
security/selinux/netlabel.c | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-)security/selinux/netlabel.c +3
-3@@ -386,11 +386,12 @@ int selinux_netlbl_inode_permission(struct inode *inode, int mask) if (!S_ISSOCK(inode->i_mode) || ((mask & (MAY_WRITE |MAY_APPEND )) ==0 ))return 0 ; - sock =SOCKET_I (inode); sk = sock->sk; +if (sk ==NULL ) +return 0 ; sksec = sk->sk_security; -if (sksec->nlbl_state !=NLBL_REQUIRE ) +if (sksec ==NULL || sksec->nlbl_state !=NLBL_REQUIRE )return 0 ;local_bh_disable (); --This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.
Signature · 8 lines
paul moore linux @ hp -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.