From f22f408956bf02609a96b7d72fb3321da159bfc6 Mon Sep 17 00:00:00 2001 From: Nico Huber Date: Tue, 22 Jun 2021 13:49:44 +0000 Subject: cbfstool: Make use of spurious null-termination The null-termination of `filetypes` was added after the code was written, obviously resulting in NULL dereferences. As some more code has grown around the termination, it's hard to revert the regression, so let's update the code that still used the array length. This fixes commit 7f5f9331d1 (util/cbfstool: fix buffer over-read) which actually did fix something, but only one path while it broke two others. We should be careful with fixes, they can always break something else. Especially when a dumb tool triggered the patching it seems likely that fewer people looked into related code. Change-Id: If2ece1f5ad62952ed2e57769702e318ba5468f0c Signed-off-by: Nico Huber Reviewed-on: https://review.coreboot.org/c/coreboot/+/55763 Tested-by: build bot (Jenkins) Reviewed-by: Julius Werner --- util/cbfstool/common.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'util') diff --git a/util/cbfstool/common.c b/util/cbfstool/common.c index e2ed38ffc4..539d0baccf 100644 --- a/util/cbfstool/common.c +++ b/util/cbfstool/common.c @@ -168,10 +168,10 @@ void print_supported_architectures(void) void print_supported_filetypes(void) { - int i, number = ARRAY_SIZE(filetypes); + int i; - for (i=0; i