security: do not check mmap_min_addr on nommu systems
Subsystems (5)
PATCH 1/1 security: do not check mmap_min_addr on nommu systems
nommu systems can do anything with memory they please and so they already win. mmap_min_addr is the least of their worries. Currently the mmap_min_addr implementation is problamatic on such systems. This patch changes the addr_only argument to be a flags which can take the arguments for addr_only or not_addr. LSMs then need to properly implement these two flags.
---
include/linux/security.h | 18 +++++++++++++----- mm/mmap.c | 6 ++++-- mm/mremap.c | 6 ++++-- mm/nommu.c | 3 ++- security/commoncap.c | 7 ++++--- security/security.c | 5 +++-- security/selinux/hooks.c | 9 +++++---- 7 files changed, 35 insertions(+), 19 deletions(-)
include/linux/security.h +13 -5
@@ -43,6 +43,12 @@#define SECURITY_CAP_NOAUDIT 0#define SECURITY_CAP_AUDIT 1 +/* sec_flags for security_file_mmap */ +/* Only check the address portion */ +#define SECURITY_MMAP_ADDR_ONLY 0x01 +/* Do not do the address checks */ +#define SECURITY_MMAP_NOT_ADDR 0x02 +struct ctl_table ;struct audit_krule ;
@@ -69,7 +75,7 @@ extern int cap_inode_need_killpriv(struct dentry *dentry);extern int cap_inode_killpriv (struct dentry *dentry);extern int cap_file_mmap (struct file *file,unsigned long reqprot,unsigned long prot,unsigned long flags, -unsigned long addr,unsigned long addr_only); +unsigned long addr,unsigned long sec_flags);extern int cap_task_fix_setuid (struct cred *new,const struct cred *old,int flags);extern int cap_task_prctl (int option,unsigned long arg2,unsigned long arg3,unsigned long arg4,unsigned long arg5);
@@ -609,6 +615,8 @@ static inline void security_free_mnt_opts(struct security_mnt_opts *opts)* @reqprot contains the protection requested by the application. * @prot contains the protection that will be applied by the kernel. * @flags contains the operational flags. +* @addr address vm will map to +* @sec_flags what security checks should be done * Return 0 if permission is granted. * @file_mprotect: * Check permissions before changing memory access permissions.
@@ -1556,7 +1564,7 @@ struct security_operations {int (*file_mmap) (struct file *file,unsigned long reqprot,unsigned long prot,unsigned long flags,unsigned long addr, -unsigned long addr_only); +unsigned long sec_flags);int (*file_mprotect) (struct vm_area_struct *vma,unsigned long reqprot,unsigned long prot);
@@ -1826,7 +1834,7 @@ void security_file_free(struct file *file);int security_file_ioctl (struct file *file,unsigned int cmd,unsigned long arg);int security_file_mmap (struct file *file,unsigned long reqprot,unsigned long prot,unsigned long flags, -unsigned long addr,unsigned long addr_only); +unsigned long addr,unsigned long sec_flags);int security_file_mprotect (struct vm_area_struct *vma,unsigned long reqprot,unsigned long prot);int security_file_lock (struct file *file,unsigned int cmd);
@@ -2323,9 +2331,9 @@ static inline int security_file_mmap(struct file *file, unsigned long reqprot,unsigned long prot, unsigned long flags, unsigned long addr, - unsigned long addr_only) + unsigned long sec_flags) { - return cap_file_mmap(file, reqprot, prot, flags, addr, addr_only); + return cap_file_mmap(file, reqprot, prot, flags, addr, sec_flags); } static inline int security_file_mprotect(struct vm_area_struct *vma,
mm/mmap.c +4 -2
@@ -1664,7 +1664,8 @@ static int expand_downwards(struct vm_area_struct *vma,return -ENOMEM ; address &=PAGE_MASK ; - error =security_file_mmap (NULL ,0 ,0 ,0 , address,1 ); + error =security_file_mmap (NULL ,0 ,0 ,0 , address, +SECURITY_MMAP_ADDR_ONLY );if (error)return error;
@@ -2005,7 +2006,8 @@ unsigned long do_brk(unsigned long addr, unsigned long len)if (is_hugepage_only_range (mm, addr, len))return -EINVAL ; - error =security_file_mmap (NULL ,0 ,0 ,0 , addr,1 ); + error =security_file_mmap (NULL ,0 ,0 ,0 , addr, +SECURITY_MMAP_ADDR_ONLY );if (error)return error;
mm/mremap.c +4 -2
@@ -313,7 +313,8 @@ unsigned long do_mremap(unsigned long addr,if ((addr <= new_addr) && (addr+old_len) > new_addr) goto out; - ret =security_file_mmap (NULL ,0 ,0 ,0 , new_addr,1 ); + ret =security_file_mmap (NULL ,0 ,0 ,0 , new_addr, +SECURITY_MMAP_ADDR_ONLY );if (ret) goto out;
@@ -421,7 +422,8 @@ unsigned long do_mremap(unsigned long addr, goto out; } - ret =security_file_mmap (NULL ,0 ,0 ,0 , new_addr,1 ); + ret =security_file_mmap (NULL ,0 ,0 ,0 , new_addr, +SECURITY_MMAP_ADDR_ONLY );if (ret) goto out; }
mm/nommu.c +2 -1
@@ -974,7 +974,8 @@ static int validate_mmap_request(struct file *file, }/* allow the security API to have its say */ - ret =security_file_mmap (file, reqprot, prot, flags, addr,0 ); + ret =security_file_mmap (file, reqprot, prot, flags,0 , +SECURITY_MMAP_NOT_ADDR );if (ret <0 )return ret;
security/commoncap.c +4 -3
@@ -924,7 +924,7 @@ int cap_vm_enough_memory(struct mm_struct *mm, long pages)* @prot: unused * @flags: unused * @addr: address attempting to be mapped -* @addr_only: unused +* @sec_flags: should the addr be checked? * * If the process is attempting to map memory below mmap_min_addr they need * CAP_SYS_RAWIO. The other parameters to this function are unused by the
@@ -933,11 +933,12 @@ int cap_vm_enough_memory(struct mm_struct *mm, long pages)*/ int cap_file_mmap (struct file *file,unsigned long reqprot,unsigned long prot,unsigned long flags, -unsigned long addr,unsigned long addr_only) +unsigned long addr,unsigned long sec_flags) {int ret =0 ; -if (addr < dac_mmap_min_addr) { +if (!(sec_flags &SECURITY_MMAP_NOT_ADDR ) && + (addr < dac_mmap_min_addr)) { ret =cap_capable (current,current_cred (),CAP_SYS_RAWIO ,SECURITY_CAP_AUDIT );/* set PF_SUPERPRIV if it turns out we allow the low mmap */
security/security.c +3 -2
@@ -677,11 +677,12 @@ int security_file_ioctl(struct file *file, unsigned int cmd, unsigned long arg)int security_file_mmap (struct file *file,unsigned long reqprot,unsigned long prot,unsigned long flags, -unsigned long addr,unsigned long addr_only) +unsigned long addr,unsigned long sec_flags) {int ret; - ret = security_ops->file_mmap (file, reqprot, prot, flags, addr, addr_only); + ret = security_ops->file_mmap (file, reqprot, prot, flags, addr, + sec_flags);if (ret)return ret;return ima_file_mmap (file, prot);
security/selinux/hooks.c +5 -4
@@ -3043,7 +3043,7 @@ error:static int selinux_file_mmap (struct file *file,unsigned long reqprot,unsigned long prot,unsigned long flags, -unsigned long addr,unsigned long addr_only) +unsigned long addr,unsigned long sec_flags) {int rc =0 ;u32 sid =current_sid ();
@@ -3054,7 +3054,8 @@ static int selinux_file_mmap(struct file *file, unsigned long reqprot,* at bad behaviour/exploit that we always want to get the AVC, even * if DAC would have also denied the operation. */ -if (addr <CONFIG_LSM_MMAP_MIN_ADDR ) { +if (!(sec_flags &SECURITY_MMAP_NOT_ADDR ) && + (addr <CONFIG_LSM_MMAP_MIN_ADDR )) { rc =avc_has_perm (sid, sid,SECCLASS_MEMPROTECT ,MEMPROTECT__MMAP_ZERO ,NULL );if (rc)
@@ -3062,8 +3063,8 @@ static int selinux_file_mmap(struct file *file, unsigned long reqprot, }/* do DAC check on address space usage */ - rc =cap_file_mmap (file, reqprot, prot, flags, addr, addr_only); -if (rc || addr_only) + rc =cap_file_mmap (file, reqprot, prot, flags, addr, sec_flags); +if (rc || (sec_flags &SECURITY_MMAP_ADDR_ONLY ))return rc;if (selinux_checkreqprot)
Andrew Morton
maintainerQuoted 6 lines · On Thu, 03 Dec 2009 14:43:01 -0500 Eric Paris <[email protected]> wrote:
nommu systems can do anything with memory they please and so they already win.
mmap_min_addris the least of their worries. Currently themmap_min_addrimplementation is problamatic on such systems. This patch changes theaddr_onlyargument to be a flags which can take the arguments foraddr_onlyornot_addr. LSMs then need to properly implement these two flags.
This replaces David's nommu-ignore-the-address-parameter-in-the-file_mmap-security-check.patch, which missed 2.6.32.
What are our thoughts wrt backporting this fix in some form into 2.6.32.x and earlier?
Quoted 10 lines · Andrew Morton
Quoted 6 lines · On Thu, 03 Dec 2009 14:43:01 -0500 Eric Paris <[email protected]> wrote:
nommu systems can do anything with memory they please and so they already win.
mmap_min_addris the least of their worries. Currently themmap_min_addrimplementation is problamatic on such systems. This patch changes theaddr_onlyargument to be a flags which can take the arguments foraddr_onlyornot_addr. LSMs then need to properly implement these two flags.
Quoted 6 lines
This replaces David's nommu-ignore-the-address-parameter-in-the-file_mmap-security-check.patch, which missed 2.6.32.
What are our thoughts wrt backporting this fix in some form into 2.6.32.x and earlier?
It would be very simple to do if anyone really wanted it. Seems the only people who hit the problem already are happy with their temporary hack. If anyone is actually hitting this bug, would actually update to a stable kernel to get the fix, and would like me to send it that way let me know and I will.
-Eric
include/linux/security.h line 50
Quoted 5 lines · Eric Paris
include/linux/security.h +5
-0+/* sec_flags for security_file_mmap */ +/* Only check the address portion */ +#define SECURITY_MMAP_ADDR_ONLY 0x01 +/* Do not do the address checks */ +#define SECURITY_MMAP_NOT_ADDR 0x02
I'm still not happy with the names assigned to these constants.
Can we call them:
#define SECURITY_MMAP_ADDR_CHECK_ONLY 0x01
#define SECURITY_MMAP_SKIP_ADDR_CHECK 0x02
and then discard the comments?
Also, the big banner comment in security.h that describes all the function pointers does not make any mention of this argument. Can you fix that too, please?
David
Quoted 3 lines · David Howells
Also, the big banner comment in
security.hthat describes all the function pointers does not make any mention of this argument. Can you fix that too, please?
Ignore that. I missed the bit of the patch where it was dealing with that.
David
Quoted 10 lines · David Howells
include/linux/security.h line 50
Quoted 5 lines · Eric Paris
include/linux/security.h +5
-0+/* sec_flags for security_file_mmap */ +/* Only check the address portion */ +#define SECURITY_MMAP_ADDR_ONLY 0x01 +/* Do not do the address checks */ +#define SECURITY_MMAP_NOT_ADDR 0x02I'm still not happy with the names assigned to these constants.
Quoted 6 lines
Can we call them:
#define
SECURITY_MMAP_ADDR_CHECK_ONLY0x01
#defineSECURITY_MMAP_SKIP_ADDR_CHECK0x02and then discard the comments?
I do like these suggested names a little better. Either way I am happy with the patch.