linux-kernel - different capability from different namespace required for prctl_set_mm_exe

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]

Message-Id: <990D0DB4-35C7-4B7B-A938-2B984CD97E78@vt.edu>
Date:   Tue, 25 Sep 2018 13:26:55 -0400
From:   Tong Zhang <ztong@...edu>
To:     tglx@...utronix.de, akpm@...ux-foundation.org,
        linux@...inikbrodowski.net, gorcunov@...nvz.org,
        ebiederm@...ssion.com, gregkh@...uxfoundation.org,
        keescook@...omium.org, Dave.Martin@....com,
        wolffhardt.schwabe@....de, yang.shi@...ux.alibaba.com
Cc:     linux-kernel@...r.kernel.org, wenbo.s@...sung.com
Subject: different capability from different namespace required for
 prctl_set_mm_exe_file

Kernel Version: 4.18.5

Problem Description:

We discovered inconsistent check when using prctl_set_mm_exe_file(), which is used to setup exe file link.

It is required to have capable(CAP_SYS_RESOURCE) in prctl_set_mm().
while ns_capable(CAP_SYS_ADMIN) in prctl_set_mm_map().

There are two differences:
1)requiring capability from: user namespace, init namespace.
2)capability bit required is different

- Tong