From: patchwork-bot+netdevbpf@kernel.org
To: Fedor Pchelkin <pchelkin@ispras.ru>
Cc: kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org,
artem.chernyshev@red-soft.ru, richardsonnick@google.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: Re: [PATCH net v2] pktgen: Avoid out-of-bounds access in get_imix_entries
Date: Mon, 13 Jan 2025 09:10:32 +0000 [thread overview]
Message-ID: <173675943251.3415908.7564815246317322659.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250109083039.14004-1-pchelkin@ispras.ru>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 9 Jan 2025 11:30:39 +0300 you wrote:
> From: Artem Chernyshev <artem.chernyshev@red-soft.ru>
>
> Passing a sufficient amount of imix entries leads to invalid access to the
> pkt_dev->imix_entries array because of the incorrect boundary check.
>
> UBSAN: array-index-out-of-bounds in net/core/pktgen.c:874:24
> index 20 is out of range for type 'imix_pkt [20]'
> CPU: 2 PID: 1210 Comm: bash Not tainted 6.10.0-rc1 #121
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)
> Call Trace:
> <TASK>
> dump_stack_lvl lib/dump_stack.c:117
> __ubsan_handle_out_of_bounds lib/ubsan.c:429
> get_imix_entries net/core/pktgen.c:874
> pktgen_if_write net/core/pktgen.c:1063
> pde_write fs/proc/inode.c:334
> proc_reg_write fs/proc/inode.c:346
> vfs_write fs/read_write.c:593
> ksys_write fs/read_write.c:644
> do_syscall_64 arch/x86/entry/common.c:83
> entry_SYSCALL_64_after_hwframe arch/x86/entry/entry_64.S:130
>
> [...]
Here is the summary with links:
- [net,v2] pktgen: Avoid out-of-bounds access in get_imix_entries
https://git.kernel.org/netdev/net/c/76201b597976
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-01-13 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 8:30 Fedor Pchelkin
2025-01-13 9:10 ` 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=173675943251.3415908.7564815246317322659.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=artem.chernyshev@red-soft.ru \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pchelkin@ispras.ru \
--cc=richardsonnick@google.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®