[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <29331004c900e82a898668459ff0f8157e6f8645.camel@linux.ibm.com>
Date: Mon, 29 Dec 2025 16:13:09 -0500
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Chris J Arges <carges@...udflare.com>, roberto.sassu@...wei.com
Cc: kernel-team@...udflare.com, Dmitry Kasatkin
<dmitry.kasatkin@...il.com>,
Eric Snowberg <eric.snowberg@...cle.com>,
Paul Moore <paul@...l-moore.com>, James Morris <jmorris@...ei.org>,
"Serge
E. Hallyn" <serge@...lyn.com>,
Mickaël Salaün
<mic@...ikod.net>,
Kees Cook <kees@...nel.org>, linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] ima: Fix stack-out-of-bounds in
is_bprm_creds_for_exec()
On Sat, 2025-12-27 at 21:18 -0600, Chris J Arges wrote:
> KASAN reported a stack-out-of-bounds access in ima_appraise_measurement
> from is_bprm_creds_for_exec:
>
> BUG: KASAN: stack-out-of-bounds in ima_appraise_measurement+0x12dc/0x16a0
> Read of size 1 at addr ffffc9000160f940 by task sudo/550
> The buggy address belongs to stack of task sudo/550
> and is located at offset 24 in frame:
> ima_appraise_measurement+0x0/0x16a0
> This frame has 2 objects:
> [48, 56) 'file'
> [80, 148) 'hash'
>
> This is caused by using container_of on the *file pointer. This offset
> calculation is what triggers the stack-out-of-bounds error.
>
> In order to fix this, pass in a bprm_is_check boolean which can be set
> depending on how process_measurement is called. If the caller has a
> linux_binprm pointer and the function is BPRM_CHECK we can determine
> is_check and set it then. Otherwise set it to false.
>
> Fixes: 95b3cdafd7cb7 ("ima: instantiate the bprm_creds_for_exec() hook")
>
> Signed-off-by: Chris J Arges <carges@...udflare.com>
Thanks, Chris. The patch is now queued in the linux-integrity/next-integrity
branch.
Mimi
Powered by blists - more mailing lists