linux-kernel - BUG: unable to handle kernel paging request in security_compute

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:   Fri, 22 Dec 2017 13:38:01 -0800
From:   syzbot 
        <bot+d10271989aa91b0c140f6c218c5537f942888ce2@...kaller.appspotmail.com>
To:     danielj@...lanox.com, dledford@...hat.com, eparis@...isplace.org,
        james.l.morris@...cle.com, junil0814.lee@....com,
        linux-kernel@...r.kernel.org,
        linux-security-module@...r.kernel.org, mka@...omium.org,
        paul@...l-moore.com, sds@...ho.nsa.gov, selinux@...ho.nsa.gov,
        serge@...lyn.com, syzkaller-bugs@...glegroups.com
Subject: BUG: unable to handle kernel paging request in security_compute_sid

Hello,

syzkaller hit the following crash on  
6084b576dca2e898f5c101baef151f7bfdbb606d
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.
C reproducer is attached
syzkaller reproducer is attached. See https://goo.gl/kgGztJ
for information about syzkaller reproducers


BUG: unable to handle kernel paging request at 00000000830e2118
IP: security_compute_sid.part.11+0x418/0x710  
security/selinux/ss/services.c:1640
PGD 0 P4D 0
Oops: 0000 [#1] SMP
Dumping ftrace buffer:
    (ftrace buffer empty)
Modules linked in:
CPU: 0 PID: 3391 Comm: kworker/u4:0 Not tainted 4.15.0-rc3-next-20171214+  
#67
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS  
Google 01/01/2011
RIP: 0010:security_compute_sid.part.11+0x418/0x710  
security/selinux/ss/services.c:1640
RSP: 0018:ffffc90001993c70 EFLAGS: 00010293
RAX: ffff880216ba0800 RBX: 0000000000000002 RCX: ffffffff81667b88
RDX: 0000000000000000 RSI: 0000000000000005 RDI: ffffffff83fd17a0
RBP: ffffc90001993d20 R08: 0000000000000001 R09: 0000000000000001
R10: ffffc90001993be0 R11: 0000000000000000 R12: ffff88021694f188
R13: 0000000000000010 R14: ffff880216592388 R15: 00000000830e20e0
FS:  0000000000000000(0000) GS:ffff88021fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000830e2118 CR3: 000000000301e001 CR4: 00000000001606f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
  security_compute_sid+0x92/0xa0 security/selinux/ss/services.c:1598
  security_transition_sid+0x57/0x70 security/selinux/ss/services.c:1764
  selinux_bprm_set_creds+0x215/0x2f0 security/selinux/hooks.c:2423
  security_bprm_set_creds+0x41/0x60 security/security.c:332
  prepare_binprm+0xae/0x1f0 fs/exec.c:1561
  do_execveat_common.isra.30+0x6f7/0xb90 fs/exec.c:1784
  do_execve+0x31/0x40 fs/exec.c:1848
  call_usermodehelper_exec_async+0x104/0x190 kernel/umh.c:100
  ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:524
Code: 40 74 15 41 83 fd 10 74 0f e8 d5 27 c5 ff 4d 85 ff 75 33 e9 6f 02 00  
00 e8 c6 27 c5 ff 4d 85 ff 0f 84 e6 02 00 00 e8 b8 27 c5 ff <41> 80 7f 38  
02 0f 84 5c 01 00 00 e8 a8 27 c5 ff 41 8b 06 89 45
RIP: security_compute_sid.part.11+0x418/0x710  
security/selinux/ss/services.c:1640 RSP: ffffc90001993c70
CR2: 00000000830e2118
---[ end trace fe59d8175af57ffc ]---
Kernel panic - not syncing: Fatal exception
Dumping ftrace buffer:
    (ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzkaller@...glegroups.com.
Please credit me with: Reported-by: syzbot <syzkaller@...glegroups.com>

syzbot will keep track of this bug report.
Once a fix for this bug is merged into any tree, reply to this email with:
#syz fix: exact-commit-title
If you want to test a patch for this bug, please reply with:
#syz test: git://repo/address.git branch
and provide the patch inline or as an attachment.
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug  
report.
Note: all commands must start from beginning of the line in the email body.

View attachment "config.txt" of type "text/plain" (126475 bytes)

Download attachment "raw.log" of type "application/octet-stream" (5284 bytes)

View attachment "repro.txt" of type "text/plain" (437 bytes)

Download attachment "repro.c" of type "application/octet-stream" (2582 bytes)