Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp179895pxf; Wed, 17 Mar 2021 19:20:32 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzu214kBrOU4ymihcKgy9Vk0qAm5Xsl5BBBQBetEx60oD4jVRkEprLukanbSQ+E+M8pqnve X-Received: by 2002:a17:906:7806:: with SMTP id u6mr17380999ejm.130.1616034031849; Wed, 17 Mar 2021 19:20:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616034031; cv=none; d=google.com; s=arc-20160816; b=TkFSy0mtIp0w+6XbVVYUO/xXaeSOAhZiYuBPJjprQeiHsph0gpjwmV5Sw2VwXC/ND6 XnpB9Nx5ic5sgUq+bj43beBPDR1HhnHO5LrDl5XfPAQgvold0jZEhvvrWXi4DchXy/OX 3ufsegsWDvKK1NM04fNLd+YzL5DILjuXakOZJFtadeuT0IH5ar+Xj9F2swNy0rn5a77E x+NCCL4tS9EtASO5G+xPfBcjp8wNfDFqeMAF37tRxQxqwQi1FM0qiqlcy+n9BOiXu1Ij i5OChZhl9yGAEo7vEEjEA4SrcEaIuBJcE7XmWfYN9lemEm4oCfUMbL5faBVX5GZjxZnq OKbw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :dkim-signature; bh=TPfXg3RCgrZBwaV5aMt9pXsKqEN0q2OLNaJFp2ggFZ8=; b=pbz0QwUap5fIHTiAWlRStHO0tSIgoEJSNsw0e/G96to/eWjqidsoiXUph+CkRE8vL1 3GX5KMTBkOaSEr9z27PI0jNmbDvNBmP4h3OuWAkJzODz4gJ7TA+DCSts5XF5gGNs9Ea0 lrPfi03qW5z4j4RE3dUBZSCjLpIG3EPG6t7TGYQ+LPt6rJjnjV1hszv1MvA1FbuYYlp6 X+WlnuZA8slthavvHOQuvDqpJMMHDWRAi2vhc0eLMhyWmhG3tvIgnxDZ94akwQGBqGS1 Ch6vgJw3CI6nKLgDmpiAmI1wIplmyk4oAS+W/PQ0PB7vt0vcWnUPRd6QWiGjgz2dOL10 oYXw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ibm.com header.s=pp1 header.b=G6pUkeRw; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m24si512371eda.304.2021.03.17.19.20.09; Wed, 17 Mar 2021 19:20:31 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@ibm.com header.s=pp1 header.b=G6pUkeRw; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230085AbhCRCTF (ORCPT + 99 others); Wed, 17 Mar 2021 22:19:05 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:43732 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229472AbhCRCSo (ORCPT ); Wed, 17 Mar 2021 22:18:44 -0400 Received: from pps.filterd (m0098396.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 12I23eML045024; Wed, 17 Mar 2021 22:18:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ibm.com; h=message-id : subject : from : to : cc : date : in-reply-to : references : content-type : mime-version : content-transfer-encoding; s=pp1; bh=TPfXg3RCgrZBwaV5aMt9pXsKqEN0q2OLNaJFp2ggFZ8=; b=G6pUkeRw8Se9uQj8gYe+RVOFDYO+kLuxsedhOc8k369zo2LVN1A1AJrA6g8rbPt2cDtq JxmN4s87yLgGmVkHpCqjr1W2+fgvyrXmCHSeFfgKlFikPM352SNjAKKm/tRYJ1ejDfZJ 4toZzteSX1PWPwpXXJnOs9q6l2qlJyOZAuPpeJ6TdErcBpx2T9PUnudHK/pHYhRBqGRD MTWla5RteBzC+vtzOU4abMltYPjXXIoLAc9HFG2n3482bWmvmY+pOJmhE12n6ZqhY/+L bFw/V4RYOdvw/nJwbqvf1qxyNo1tHUAZuEYXprt8S7lSdXNU31AwjApzDuF2cfwlRCY3 UQ== Received: from pps.reinject (localhost [127.0.0.1]) by mx0a-001b2d01.pphosted.com with ESMTP id 37bs2kqjv6-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 17 Mar 2021 22:18:31 -0400 Received: from m0098396.ppops.net (m0098396.ppops.net [127.0.0.1]) by pps.reinject (8.16.0.43/8.16.0.43) with SMTP id 12I251bN048580; Wed, 17 Mar 2021 22:18:31 -0400 Received: from ppma04fra.de.ibm.com (6a.4a.5195.ip4.static.sl-reverse.com [149.81.74.106]) by mx0a-001b2d01.pphosted.com with ESMTP id 37bs2kqjum-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 17 Mar 2021 22:18:31 -0400 Received: from pps.filterd (ppma04fra.de.ibm.com [127.0.0.1]) by ppma04fra.de.ibm.com (8.16.0.43/8.16.0.43) with SMTP id 12I2GbNv023826; Thu, 18 Mar 2021 02:18:28 GMT Received: from b06cxnps4075.portsmouth.uk.ibm.com (d06relay12.portsmouth.uk.ibm.com [9.149.109.197]) by ppma04fra.de.ibm.com with ESMTP id 37b6xjghfa-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 18 Mar 2021 02:18:28 +0000 Received: from d06av23.portsmouth.uk.ibm.com (d06av23.portsmouth.uk.ibm.com [9.149.105.59]) by b06cxnps4075.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 12I2IP3831785354 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 18 Mar 2021 02:18:26 GMT Received: from d06av23.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id D75B1A4051; Thu, 18 Mar 2021 02:18:25 +0000 (GMT) Received: from d06av23.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id B1751A4040; Thu, 18 Mar 2021 02:18:23 +0000 (GMT) Received: from li-f45666cc-3089-11b2-a85c-c57d1a57929f.ibm.com (unknown [9.163.1.108]) by d06av23.portsmouth.uk.ibm.com (Postfix) with ESMTP; Thu, 18 Mar 2021 02:18:23 +0000 (GMT) Message-ID: Subject: Re: NULL deref in integrity_inode_get From: Mimi Zohar To: Dmitry Vyukov Cc: James Morris , "Serge E. Hallyn" , linux-security-module , LKML , d.kasatkin@samsung.com, Mimi Zohar , Eric Biggers Date: Wed, 17 Mar 2021 22:18:22 -0400 In-Reply-To: References: <31c4e1863a561c47d38b8e547ec38a0a713bdadc.camel@linux.ibm.com> Content-Type: text/plain; charset="ISO-8859-15" X-Mailer: Evolution 3.28.5 (3.28.5-14.el8) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369,18.0.761 definitions=2021-03-17_16:2021-03-17,2021-03-17 signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 mlxscore=0 lowpriorityscore=0 phishscore=0 malwarescore=0 impostorscore=0 suspectscore=0 adultscore=0 clxscore=1015 mlxlogscore=928 spamscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2103180014 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Dmitry, On Mon, 2021-03-15 at 14:07 +0100, Dmitry Vyukov wrote: > On Mon, Mar 15, 2021 at 1:41 PM Mimi Zohar wrote: > > > > On Mon, 2021-03-15 at 11:58 +0100, Dmitry Vyukov wrote: > > > Hi, > > > > > > I am trying to boot 5.12-rc3 with this config: > > > https://github.com/google/syzkaller/blob/cc1cff8f1e1a585894796d6eae8c51eef98037e6/dashboard/config/linux/upstream-smack-kasan.config > > > > > > in qemu: > > > qemu-system-x86_64 -enable-kvm -machine q35,nvdimm -cpu > > > max,migratable=off -smp 4 -m 4G,slots=4,maxmem=16G -hda > > > wheezy.img -kernel arch/x86/boot/bzImage -nographic -vga std > > > -soundhw all -usb -usbdevice tablet -bt hci -bt device:keyboard > > > -net user,host=10.0.2.10,hostfwd=tcp::10022-:22 -net > > > nic,model=virtio-net-pci -object > > > memory-backend-file,id=pmem1,share=off,mem-path=/dev/zero,size=64M > > > -device nvdimm,id=nvdimm1,memdev=pmem1 -append "console=ttyS0 > > > root=/dev/sda earlyprintk=serial rodata=n oops=panic panic_on_warn=1 > > > panic=86400 lsm=smack numa=fake=2 nopcid dummy_hcd.num=8" -pidfile > > > vm_pid -m 2G -cpu host > > > > > > But it crashes on NULL deref in integrity_inode_get during boot: > > > > > > Run /sbin/init as init process > > > BUG: kernel NULL pointer dereference, address: 000000000000001c > > > #PF: supervisor read access in kernel mode > > > #PF: error_code(0x0000) - not-present page > > > PGD 0 P4D 0 > > > Oops: 0000 [#1] PREEMPT SMP KASAN > > > CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.12.0-rc2+ #97 > > > Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS > > > rel-1.13.0-44-g88ab0c15525c-prebuilt.qemu.org 04/01/2014 > > > RIP: 0010:kmem_cache_alloc+0x2b/0x370 mm/slub.c:2920 > > > Code: 57 41 56 41 55 41 54 41 89 f4 55 48 89 fd 53 48 83 ec 10 44 8b > > > 3d d9 1f 90 0b 65 48 8b 04 25 28 00 00 00 48 89 44 24 08 31 c0 <8b> 5f > > > 1c 4cf > > > RSP: 0000:ffffc9000032f9d8 EFLAGS: 00010246 > > > RAX: 0000000000000000 RBX: ffff888017fc4f00 RCX: 0000000000000000 > > > RDX: ffff888040220000 RSI: 0000000000000c40 RDI: 0000000000000000 > > > RBP: 0000000000000000 R08: 0000000000000000 R09: ffff888019263627 > > > R10: ffffffff83937cd1 R11: 0000000000000000 R12: 0000000000000c40 > > > R13: ffff888019263538 R14: 0000000000000000 R15: 0000000000ffffff > > > FS: 0000000000000000(0000) GS:ffff88802d180000(0000) knlGS:0000000000000000 > > > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > > > CR2: 000000000000001c CR3: 000000000b48e000 CR4: 0000000000750ee0 > > > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > > > DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 > > > PKRU: 55555554 > > > Call Trace: > > > integrity_inode_get+0x47/0x260 security/integrity/iint.c:105 > > > process_measurement+0x33d/0x17e0 security/integrity/ima/ima_main.c:237 > > > ima_bprm_check+0xde/0x210 security/integrity/ima/ima_main.c:474 > > > security_bprm_check+0x7d/0xa0 security/security.c:845 > > > search_binary_handler fs/exec.c:1708 [inline] > > > exec_binprm fs/exec.c:1761 [inline] > > > bprm_execve fs/exec.c:1830 [inline] > > > bprm_execve+0x764/0x19a0 fs/exec.c:1792 > > > kernel_execve+0x370/0x460 fs/exec.c:1973 > > > try_to_run_init_process+0x14/0x4e init/main.c:1366 > > > kernel_init+0x11d/0x1b8 init/main.c:1477 > > > ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294 > > > Modules linked in: > > > CR2: 000000000000001c > > > ---[ end trace 22d601a500de7d79 ]--- > > > > It looks like integrity_inode_get() fails to alloc memory. Only on > > failure to verify the integrity of a file would an error be returned. > > I think that is what you would want to happen. Without an "appraise" > > policy, this shouldn't happen. > > It happens at the very boot. I think the cache is NULL. An IMA policy had to have been loaded in order for integrity_inode_get() to have been called. If this is happening on boot, it's too early for a custom policy to have been loaded by userspace, but I don't see the builtin policy defined on the boot command line either. Any additional information would be much appreciated. thanks, Mimi