From: Bill Wendling <isanbard@gmail.com>
To: Bill Wendling <morbo@google.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Randy Dunlap <rdunlap@infradead.org>
Subject: [PATCH v3] kconfig: check for a NULL pointer before access
Date: Fri, 23 May 2025 17:49:08 -0700 [thread overview]
Message-ID: <27de0526-0b19-4e14-8c51-1e8b0ddcf490@gmail.com> (raw)
In-Reply-To: <CAGG=3QVw5+4-7f+gMJSanb0ixC=SujDQyA1=CPRvR+a6+c0U_Q@mail.gmail.com>
The call to 'prop_get_symbol' may return NULL in some cases. The if-then
statement accesses the returned value without cheecking if it's
non-NULL. After inlining, the compiler may treat the conditional as
'undefined behavior', which the compiler may take the opportunity to do
whatever it wants with the UB path. This patch simply adds a check to
ensure that 'def_sym' is non-NULL to avoid this behavior.
Signed-off-by: Bill Wendling <isanbard@gmail.com>
---
Cc: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
v3:
- Fix whitespace for real now.
- Patch from another email account so that the whitespace is retained.
v2:
- Fix whitespace
---
scripts/kconfig/symbol.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/kconfig/symbol.c b/scripts/kconfig/symbol.c
index d57f8cbba291..9c5068225328 100644
--- a/scripts/kconfig/symbol.c
+++ b/scripts/kconfig/symbol.c
@@ -272,7 +272,7 @@ struct symbol *sym_choice_default(struct menu *choice)
if (prop->visible.tri == no)
continue;
def_sym = prop_get_symbol(prop);
- if (def_sym->visible != no)
+ if (def_sym && def_sym->visible != no)
return def_sym;
}
--
2.49.0.1164.gab81da1b16-goog
next prev parent reply other threads:[~2025-05-24 0:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 0:07 [PATCH] " Bill Wendling
2025-05-23 0:16 ` Randy Dunlap
2025-05-23 22:56 ` Bill Wendling
2025-05-23 23:47 ` Randy Dunlap
2025-05-24 0:35 ` Bill Wendling
2025-05-23 22:55 ` [PATCH v2] " Bill Wendling
2025-05-24 0:49 ` Bill Wendling [this message]
2025-05-24 2:13 ` [PATCH v3] " Randy Dunlap
2025-05-24 17:07 ` Masahiro Yamada
2025-05-26 8:08 ` Bill Wendling
2025-06-27 0:42 ` [PATCH v4] " Bill Wendling
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=27de0526-0b19-4e14-8c51-1e8b0ddcf490@gmail.com \
--to=isanbard@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=morbo@google.com \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®