All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Jiayuan Chen" <jiayuan.chen@linux.dev>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf v2 2/4] bpf: Fix NULL-ptr-deref when showing a void BTF type
Date: Sun, 30 Aug 2026 07:58:48 +0000	[thread overview]
Message-ID: <20260830075849.10EE01F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260830073242.148092-3-jiayuan.chen@linux.dev>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:

Pre-existing issues:
- [High] NULL pointer dereference in `btf_var_show()` when rendering vmlinux BTF types via `bpf_snprintf_btf()`.
--

commit f9ef7fc1b664c580ca28b8d18cae855dd7b0e940
Author: Jiayuan Chen <jiayuan.chen@linux.dev>

bpf: Fix NULL-ptr-deref when showing a void BTF type

This patch fixes a NULL pointer dereference when btf_modifier_show() attempts
to render a void type. Because void lacks a show op, it falls back to
btf_df_show() instead of dereferencing a NULL pointer.

> diff --git a/kernel/bpf/btf.c b/kernel/bpf/btf.c
> index da36d4b9d31ab..81506cbb9f9ae 100644
> --- a/kernel/bpf/btf.c
> +++ b/kernel/bpf/btf.c
> @@ -2911,7 +2911,15 @@ static void btf_modifier_show(const struct btf *btf,
>  	else
>  		t = btf_type_skip_modifiers(btf, type_id, NULL);
>  
> -	btf_type_ops(t)->show(btf, t, type_id, data, bits_offset, show);
> +	/*
> +	 * A modifier can resolve to the void type (e.g. "const void"), which
> +	 * has no show op (kind_ops[BTF_KIND_UNKN] is NULL). Print a placeholder
> +	 * instead of dereferencing NULL.
> +	 */
> +	if (!btf_type_ops(t))
> +		btf_df_show(btf, t, type_id, data, bits_offset, show);
> +	else
> +		btf_type_ops(t)->show(btf, t, type_id, data, bits_offset, show);
>  }
>  
>  static void btf_var_show(const struct btf *btf, const struct btf_type *t,
>  			 u32 type_id, void *data, u8 bits_offset,
>  			 struct btf_show *show)
>  {
>  	t = btf_type_id_resolve(btf, &type_id);

[Severity: High]
This isn't a bug introduced by this patch, but while looking at this fix, I
noticed a potential issue in btf_var_show() just below it.

Can btf_var_show() cause a NULL pointer dereference when rendering vmlinux
BTF types via bpf_snprintf_btf()?

If a BPF program calls the bpf_snprintf_btf() helper and passes the type ID
of a BTF_KIND_VAR from the vmlinux BTF, formatting will dispatch to
btf_var_show().

This function unconditionally calls btf_type_id_resolve(), which attempts to
dereference btf->resolved_ids.

However, since type resolution is skipped for base BTF during parsing,
btf->resolved_ids is NULL for vmlinux BTF. Does this unconditionally result in
a NULL pointer dereference inside btf_type_id_resolve()?

>  
>  	btf_type_ops(t)->show(btf, t, type_id, data, bits_offset, show);
>  }

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260830073242.148092-1-jiayuan.chen@linux.dev?part=2

  reply	other threads:[~2026-08-30  7:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-30  7:30 [PATCH bpf v2 0/4] bpf: Fix NULL-ptr-derefs when showing a void BTF type Jiayuan Chen
2026-08-30  7:30 ` [PATCH bpf v2 1/4] bpf: Reject key-less BTF for hash maps Jiayuan Chen
2026-08-30  8:35   ` bot+bpf-ci
2026-08-30  7:30 ` [PATCH bpf v2 2/4] bpf: Fix NULL-ptr-deref when showing a void BTF type Jiayuan Chen
2026-08-30  7:58   ` sashiko-bot [this message]
2026-08-30  7:30 ` [PATCH bpf v2 3/4] selftests/bpf: Add test for key-less BTF hash map Jiayuan Chen
2026-08-30  8:35   ` bot+bpf-ci
2026-08-30  7:30 ` [PATCH bpf v2 4/4] selftests/bpf: Add test for showing a void BTF type Jiayuan Chen
2026-08-30  8:35   ` bot+bpf-ci

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=20260830075849.10EE01F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=jiayuan.chen@linux.dev \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.