public inbox for linux-trace-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Josh Law <objecting@objecting.org>
To: Masami Hiramatsu <mhiramat@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	Josh Law <objecting@objecting.org>
Subject: [PATCH v8 04/13] lib/bootconfig: increment xbc_node_num after node init succeeds
Date: Wed, 18 Mar 2026 15:59:10 +0000	[thread overview]
Message-ID: <20260318155919.78168-5-objecting@objecting.org> (raw)
In-Reply-To: <20260318155919.78168-1-objecting@objecting.org>

Move the xbc_node_num increment to after xbc_init_node() so a failed
init does not leave a partially initialized node counted in the array.

If xbc_init_node() fails on a data offset at the boundary of a
maximum-size bootconfig, the pre-incremented count causes subsequent
tree verification and traversal to consider the uninitialized node as
valid, potentially leading to an out-of-bounds read or unpredictable
boot behavior.

Signed-off-by: Josh Law <objecting@objecting.org>
---
 lib/bootconfig.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/lib/bootconfig.c b/lib/bootconfig.c
index ca668ead1db6..6b899e24189c 100644
--- a/lib/bootconfig.c
+++ b/lib/bootconfig.c
@@ -429,9 +429,10 @@ static struct xbc_node * __init xbc_add_node(char *data, uint16_t flag)
 	if (xbc_node_num == XBC_NODE_MAX)
 		return NULL;
 
-	node = &xbc_nodes[xbc_node_num++];
+	node = &xbc_nodes[xbc_node_num];
 	if (xbc_init_node(node, data, flag) < 0)
 		return NULL;
+	xbc_node_num++;
 
 	return node;
 }
-- 
2.34.1


  parent reply	other threads:[~2026-03-18 15:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-18 15:59 [PATCH v8 00/13] bootconfig: cleanups, correctness, and modernization Josh Law
2026-03-18 15:59 ` [PATCH v8 01/13] lib/bootconfig: clean up comment typos and bracing Josh Law
2026-03-18 15:59 ` [PATCH v8 02/13] lib/bootconfig: narrow flag parameter type from uint32_t to uint16_t Josh Law
2026-03-18 15:59 ` [PATCH v8 03/13] lib/bootconfig: fix off-by-one in xbc_verify_tree() next node check Josh Law
2026-03-18 15:59 ` Josh Law [this message]
2026-03-18 15:59 ` [PATCH v8 05/13] lib/bootconfig: drop redundant memset of xbc_nodes Josh Law
2026-03-18 20:22   ` Markus Elfring
2026-03-18 15:59 ` [PATCH v8 06/13] bootconfig: constify xbc_calc_checksum() data parameter Josh Law
2026-03-18 15:59 ` [PATCH v8 07/13] lib/bootconfig: replace linux/kernel.h with specific includes Josh Law
2026-03-18 15:59 ` [PATCH v8 08/13] lib/bootconfig: validate child node index in xbc_verify_tree() Josh Law
2026-03-18 15:59 ` [PATCH v8 09/13] lib/bootconfig: fix signed comparison in xbc_node_get_data() Josh Law
2026-03-18 15:59 ` [PATCH v8 10/13] lib/bootconfig: use size_t for strlen result in xbc_node_match_prefix() Josh Law
2026-03-18 15:59 ` [PATCH v8 11/13] lib/bootconfig: use signed type for offset in xbc_init_node() Josh Law
2026-03-18 15:59 ` [PATCH v8 12/13] lib/bootconfig: use size_t for key length tracking in xbc_verify_tree() Josh Law
2026-03-18 15:59 ` [PATCH v8 13/13] lib/bootconfig: change xbc_node_index() return type to uint16_t Josh Law

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260318155919.78168-5-objecting@objecting.org \
    --to=objecting@objecting.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox