mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Varun R Mallya <varunrmallya@gmail.com>
Cc: andrii@kernel.org, alan.maguire@oracle.com, ast@kernel.org,
	daniel@iogearbox.net, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org, harrisonmichaelgreen@gmail.com
Subject: Re: [PATCH bpf] libbpf: Fix OOB read in btf_dump_get_bitfield_value
Date: Sat, 10 Jan 2026 00:00:06 +0000	[thread overview]
Message-ID: <176800320632.431515.385277926966372587.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260106233527.163487-1-varunrmallya@gmail.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Wed,  7 Jan 2026 05:05:27 +0530 you wrote:
> When dumping bitfield data, btf_dump_get_bitfield_value() reads data
> based on the underlying type's size (t->size). However, it does not
> verify that the provided data buffer (data_sz) is large enough to
> contain these bytes.
> 
> If btf_dump__dump_type_data() is called with a buffer smaller than
> the type's size, this leads to an out-of-bounds read. This was
> confirmed by AddressSanitizer in the linked issue.
> 
> [...]

Here is the summary with links:
  - [bpf] libbpf: Fix OOB read in btf_dump_get_bitfield_value
    https://git.kernel.org/bpf/bpf-next/c/5714ca8cba5e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-01-10  0:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06 23:35 Varun R Mallya
2026-01-10  0:00 ` patchwork-bot+netdevbpf [this message]

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=176800320632.431515.385277926966372587.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alan.maguire@oracle.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=harrisonmichaelgreen@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=varunrmallya@gmail.com \
    /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®