linux-kernel - Leaking path for set_task

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: <F7DFF547-5267-4EF3-8BF3-70DAF6C2A53A@vt.edu>
Date:   Tue, 25 Sep 2018 13:27:08 -0400
From:   Tong Zhang <ztong@...edu>
To:     adobriyan@...il.com, akpm@...ux-foundation.org,
        viro@...iv.linux.org.uk, gorcunov@...nvz.org
Cc:     linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
        linux-security-module@...r.kernel.org, wenbo.s@...sung.com
Subject: Leaking path for set_task_comm

Kernel Version: 4.18.5

Problem Description:

When using prctl(PR_SET_NAME) to set the thread name, it is checked by security_task_prctl.

We discovered a leaking path that can also use method implemented in 
fs/proc/base.c:1526 comm_write(), to do similar thing without asking LSM’s decision.

- Tong