[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<172949702701.158018.10159023960239041535.git-patchwork-notify@kernel.org>
Date: Mon, 21 Oct 2024 07:50:27 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Peter Collingbourne <pcc@...gle.com>
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
martin.lau@...ux.dev, eddyz87@...il.com, song@...nel.org,
yonghong.song@...ux.dev, john.fastabend@...il.com, kpsingh@...nel.org,
sdf@...ichev.me, haoluo@...gle.com, jolsa@...nel.org, puranjay12@...il.com,
xukuohai@...weicloud.com, catalin.marinas@....com, will@...nel.org,
jean-philippe@...aro.org, bpf@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
glider@...gle.com, andreyknvl@...il.com, stable@...r.kernel.org
Subject: Re: [PATCH] bpf, arm64: Fix address emission with tag-based KASAN enabled
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@...earbox.net>:
On Fri, 18 Oct 2024 15:16:43 -0700 you wrote:
> When BPF_TRAMP_F_CALL_ORIG is enabled, the address of a bpf_tramp_image
> struct on the stack is passed during the size calculation pass and
> an address on the heap is passed during code generation. This may
> cause a heap buffer overflow if the heap address is tagged because
> emit_a64_mov_i64() will emit longer code than it did during the size
> calculation pass. The same problem could occur without tag-based
> KASAN if one of the 16-bit words of the stack address happened to
> be all-ones during the size calculation pass. Fix the problem by
> assuming the worst case (4 instructions) when calculating the size
> of the bpf_tramp_image address emission.
>
> [...]
Here is the summary with links:
- bpf, arm64: Fix address emission with tag-based KASAN enabled
https://git.kernel.org/bpf/bpf/c/a552e2ef5fd1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists