From nobody Mon Feb 9 06:08:58 2026 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D062B29CB52; Tue, 27 Jan 2026 14:18:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769523523; cv=none; b=hRTBcTt9Sn8ww1aAFBhkfUS3J1gRjcIRhRwslcQhXlzOOmoOCWp51B91DTLPNBjFZ+ubsEQeREJxLITitnPEqdc4ZZ7zJkGN6C620MqdgmungaIxG2DQxjtwkyZ/hTOSxRF8WWW2z5JgeryMR4IGnS404AFdBnINFMgDHoJBrHo= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769523523; c=relaxed/simple; bh=7F+DuBXgqrT8V7DZYt5hv7YfSndw1OccpW3faDSstLI=; h=From:Date:Subject:MIME-Version:Content-Type:Message-Id:To:Cc; b=NN/uHFcMr/4wu/SXk35i3m5q3VyRLL9Oby0r8ym+8bGS9j6Jg32nXw24nXMG64i3b4xfugcAowP0qnKhNPhoQuUNiyidLA/K0iKEd2hCnQ65WwwaENKOg3gxavq+pB1cZn5+fPRZyxOcshQCnR4lgJ6P3mMFUGfX1Sa4UWufGfM= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=cCoO05KW; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="cCoO05KW" Received: by smtp.kernel.org (Postfix) with ESMTPS id AF729C116C6; Tue, 27 Jan 2026 14:18:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1769523523; bh=7F+DuBXgqrT8V7DZYt5hv7YfSndw1OccpW3faDSstLI=; h=From:Date:Subject:To:Cc:Reply-To:From; b=cCoO05KW0GyDw8VD4ULQ19cydsNPmy0iuhVEfZUbFqcyHAHsOjlhidlX8hvLO+2yW xa+COWoj7ZB6NlK7VrSPa7Z4hPAwlPSZ5fxaQAyOeEhcBMk5AVn55jNx7fS0NkAY9w wN/qsMWunwQiivVczHsPwNrjx1M6y+tuN52y2Co5DAqQAaTUqtsL1nCjelXFA/kFw0 9ShgLK+VtIBTQq9E1z2LWbCe3ptrWuCGv4KewHBwZbkvdMqVM1+YmremuBYRhX47Ef nUleni6zSTzFQswU8CcV8ml3oHhVsvx9XHjinXmjF+w0pJJNWuKo5p/ScLfjQXVELv SMd6ktwPb+gng== Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9C437D2F037; Tue, 27 Jan 2026 14:18:43 +0000 (UTC) From: Dmitry Safonov via B4 Relay Date: Tue, 27 Jan 2026 14:18:28 +0000 Subject: [PATCH v2] ima_fs: Avoid creating measurement lists for unsupported hash algos Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <20260127-ima-oob-v2-1-f38a18c850cf@arista.com> X-B4-Tracking: v=1; b=H4sIADPJeGkC/2WNMQ6DMAxFr4I81xUJFGin3qNicMAUDxDkoKgV4 u4NrB2f9P77GwRW4QCPbAPlKEH8nMBeMuhGmt+M0icGm9sqN7ZGmQi9d3gfqCmoKsq+dpDsRXm Qz1l6tYkdBUanNHfjsZ8orKyHOEpYvX7Px2gO/T8eDRq0fWmHojQN3+onaZrRtfMTtPu+/wDh+ OWjuAAAAA== X-Change-ID: 20260127-ima-oob-9fa83a634d7b To: Mimi Zohar , Roberto Sassu , Dmitry Kasatkin , Eric Snowberg , Paul Moore , James Morris , "Serge E. Hallyn" , Silvia Sisinni , Enrico Bravi Cc: linux-integrity@vger.kernel.org, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org, Dmitry Safonov <0x7f454c46@gmail.com>, Dmitry Safonov X-Mailer: b4 0.14.3 X-Developer-Signature: v=1; a=ed25519-sha256; t=1769523522; l=5995; i=dima@arista.com; s=20250521; h=from:subject:message-id; bh=ioQ0EdzWsdpfxVjATXSELCB4MMNH/LYwAsBPTDyyGPs=; b=dAXkvPTNBGVwDXnCdQxTg8IdAnpL305I+CaRbmgOZvx/DGly4StwaALRji1PqJrNK7dRdxThB tFlyQ+vfTWcC7ZtiF4wOlLPwMus+0MZxIVY6WHVKBXcMH5BtshEgKUL X-Developer-Key: i=dima@arista.com; a=ed25519; pk=/z94x2T59rICwjRqYvDsBe0MkpbkkdYrSW2J1G2gIcU= X-Endpoint-Received: by B4 Relay for dima@arista.com/20250521 with auth_id=405 X-Original-From: Dmitry Safonov Reply-To: dima@arista.com From: Dmitry Safonov ima_init_crypto() skips initializing ima_algo_array[i] if the alogorithm from ima_tpm_chip->allocated_banks[i].crypto_id is not supported. It seems avoid adding the unsupported algorithm to ima_algo_array will break all the logic that relies on indexing by NR_BANKS(ima_tpm_chip). On 6.12.40 I observe the following read out-of-bounds in hash_algo_name: > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > BUG: KASAN: global-out-of-bounds in create_securityfs_measurement_lists+0= x396/0x440 > Read of size 8 at addr ffffffff83e18138 by task swapper/0/1 > > CPU: 4 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.40 #3 > Call Trace: > > dump_stack_lvl+0x61/0x90 > print_report+0xc4/0x580 > ? kasan_addr_to_slab+0x26/0x80 > ? create_securityfs_measurement_lists+0x396/0x440 > kasan_report+0xc2/0x100 > ? create_securityfs_measurement_lists+0x396/0x440 > create_securityfs_measurement_lists+0x396/0x440 > ima_fs_init+0xa3/0x300 > ima_init+0x7d/0xd0 > init_ima+0x28/0x100 > do_one_initcall+0xa6/0x3e0 > kernel_init_freeable+0x455/0x740 > kernel_init+0x24/0x1d0 > ret_from_fork+0x38/0x80 > ret_from_fork_asm+0x11/0x20 > > > The buggy address belongs to the variable: > hash_algo_name+0xb8/0x420 > > The buggy address belongs to the physical page: > page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x107c= e18 > flags: 0x8000000000002000(reserved|zone=3D2) > raw: 8000000000002000 ffffea0041f38608 ffffea0041f38608 0000000000000000 > raw: 0000000000000000 0000000000000000 00000001ffffffff 0000000000000000 > page dumped because: kasan: bad access detected > > Memory state around the buggy address: > ffffffff83e18000: 00 01 f9 f9 f9 f9 f9 f9 00 01 f9 f9 f9 f9 f9 f9 > ffffffff83e18080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > >ffffffff83e18100: 00 00 00 00 00 00 00 f9 f9 f9 f9 f9 00 05 f9 f9 > ^ > ffffffff83e18180: f9 f9 f9 f9 00 00 00 00 00 00 00 04 f9 f9 f9 f9 > ffffffff83e18200: 00 00 00 00 00 00 00 00 04 f9 f9 f9 f9 f9 f9 f9 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Seems like the TPM chip supports sha3_256, which isn't yet in tpm_algorithms: > tpm tpm0: TPM with unsupported bank algorithm 0x0027 Grepping HASH_ALGO__LAST in security/integrity/ima/ shows that is the check other logic relies on, so add files under TPM_ALG_ and print 0 as their hash_digest_size. This is how it looks on the test machine I have: > # ls -1 /sys/kernel/security/ima/ > ascii_runtime_measurements > ascii_runtime_measurements_TPM_ALG_27 > ascii_runtime_measurements_sha1 > ascii_runtime_measurements_sha256 > binary_runtime_measurements > binary_runtime_measurements_TPM_ALG_27 > binary_runtime_measurements_sha1 > binary_runtime_measurements_sha256 > policy > runtime_measurements_count > violations Fixes: 9fa8e7625008 ("ima: add crypto agility support for template-hash alg= orithm") Signed-off-by: Dmitry Safonov Cc: Enrico Bravi Cc: Silvia Sisinni Cc: Roberto Sassu Cc: Mimi Zohar --- Changes in v2: - Instead of skipping unknown algorithms, add files under their TPM_ALG_ID = (Roberto Sassu) - Fix spelling (Roberto Sassu) - Copy @stable on the fix - Link to v1: https://lore.kernel.org/r/20260127-ima-oob-v1-1-2d42f3418e57@= arista.com --- security/integrity/ima/ima_fs.c | 26 ++++++++++++++++++++------ 1 file changed, 20 insertions(+), 6 deletions(-) diff --git a/security/integrity/ima/ima_fs.c b/security/integrity/ima/ima_f= s.c index 012a58959ff0..3b442e3f84d0 100644 --- a/security/integrity/ima/ima_fs.c +++ b/security/integrity/ima/ima_fs.c @@ -160,7 +160,10 @@ int ima_measurements_show(struct seq_file *m, void *v) ima_putc(m, &pcr, sizeof(e->pcr)); =20 /* 2nd: template digest */ - ima_putc(m, e->digests[algo_idx].digest, hash_digest_size[algo]); + if (algo =3D=3D HASH_ALGO__LAST) + ima_putc(m, "0", 1); + else + ima_putc(m, e->digests[algo_idx].digest, hash_digest_size[algo]); =20 /* 3rd: template name size */ namelen =3D !ima_canonical_fmt ? strlen(template_name) : @@ -252,7 +255,10 @@ static int ima_ascii_measurements_show(struct seq_file= *m, void *v) seq_printf(m, "%2d ", e->pcr); =20 /* 2nd: template hash */ - ima_print_digest(m, e->digests[algo_idx].digest, hash_digest_size[algo]); + if (algo =3D=3D HASH_ALGO__LAST) + ima_putc(m, "0", 1); + else + ima_print_digest(m, e->digests[algo_idx].digest, hash_digest_size[algo]); =20 /* 3th: template name */ seq_printf(m, " %s", template_name); @@ -404,16 +410,24 @@ static int __init create_securityfs_measurement_lists= (void) char file_name[NAME_MAX + 1]; struct dentry *dentry; =20 - sprintf(file_name, "ascii_runtime_measurements_%s", - hash_algo_name[algo]); + if (algo =3D=3D HASH_ALGO__LAST) + sprintf(file_name, "ascii_runtime_measurements_TPM_ALG_%x", + ima_tpm_chip->allocated_banks[i].alg_id); + else + sprintf(file_name, "ascii_runtime_measurements_%s", + hash_algo_name[algo]); dentry =3D securityfs_create_file(file_name, S_IRUSR | S_IRGRP, ima_dir, (void *)(uintptr_t)i, &ima_ascii_measurements_ops); if (IS_ERR(dentry)) return PTR_ERR(dentry); =20 - sprintf(file_name, "binary_runtime_measurements_%s", - hash_algo_name[algo]); + if (algo =3D=3D HASH_ALGO__LAST) + sprintf(file_name, "binary_runtime_measurements_TPM_ALG_%x", + ima_tpm_chip->allocated_banks[i].alg_id); + else + sprintf(file_name, "binary_runtime_measurements_%s", + hash_algo_name[algo]); dentry =3D securityfs_create_file(file_name, S_IRUSR | S_IRGRP, ima_dir, (void *)(uintptr_t)i, &ima_measurements_ops); --- base-commit: 63804fed149a6750ffd28610c5c1c98cce6bd377 change-id: 20260127-ima-oob-9fa83a634d7b Best regards, --=20 Dmitry Safonov