linux-kernel - [RFC PATCH] Security: ignore private inode from security_file

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 16 Apr 2015 22:40:56 +0900
From:	Seung-Woo Kim <sw0312.kim@...sung.com>
To:	james.l.morris@...cle.com, serge@...lyn.com,
	linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:	sw0312.kim@...sung.com, sumit.semwal@...aro.org,
	linaro-mm-sig@...ts.linaro.org, jy0922.shim@...sung.com
Subject: [RFC PATCH] Security: ignore private inode from security_file_receive

The dma-buf fd from anon_inode can be shared across processes, but
there is no way to set security permission for the fd. So this
patch fix just to ignore private inode from security_file_receive.

Signed-off-by: Seung-Woo Kim <sw0312.kim@...sung.com>
---

If security like smack is enabled, the dmabuf fd can not be shared between
processes via unix domain socket. I am not familiar with security, so I am
not sure that this kind of patch can be acceptable.

Is there other option to share dmabuf fd via socket with security check?

Best Regards,
- Seung-Woo Kim

---
 security/security.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/security/security.c b/security/security.c
index 730ac65..c57354c 100644
--- a/security/security.c
+++ b/security/security.c
@@ -810,6 +810,9 @@ int security_file_send_sigiotask(struct task_struct *tsk,
 
 int security_file_receive(struct file *file)
 {
+
+	if (unlikely(IS_PRIVATE(file->f_path.dentry->d_inode)))
+		return 0;
 	return security_ops->file_receive(file);
 }
 
-- 
1.7.4.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/