From: Will Deacon <will@kernel.org>
To: Fuad Tabba <tabba@google.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Puranjay Mohan <puranjay@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
bpf@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
Xu Kuohai <xukuohai@huaweicloud.com>,
Jakub Sitnicki <jakub@cloudflare.com>,
Jean-Philippe Brucker <jpb@kernel.org>
Subject: Re: [PATCH v3] arm64: bpf: Force 8-byte alignment for JIT buffer to prevent atomic tearing
Date: Thu, 26 Feb 2026 18:28:32 +0000 [thread overview]
Message-ID: <aaCQ0M9h1QfCPKGb@willie-the-truck> (raw)
In-Reply-To: <20260226075525.233321-1-tabba@google.com>
On Thu, Feb 26, 2026 at 07:55:25AM +0000, Fuad Tabba wrote:
> struct bpf_plt contains a u64 target field. Currently, the BPF JIT
> allocator requests an alignment of 4 bytes (sizeof(u32)) for the JIT
> buffer.
>
> Because the base address of the JIT buffer can be 4-byte aligned (e.g.,
> ending in 0x4 or 0xc), the relative padding logic in build_plt() fails
> to ensure that target lands on an 8-byte boundary.
>
> This leads to two issues:
> 1. UBSAN reports misaligned-access warnings when dereferencing the
> structure.
> 2. More critically, target is updated concurrently via WRITE_ONCE() in
> bpf_arch_text_poke() while the JIT'd code executes ldr. On arm64,
> 64-bit loads/stores are only guaranteed to be single-copy atomic if
> they are 64-bit aligned. A misaligned target risks a torn read,
> causing the JIT to jump to a corrupted address.
>
> Fix this by increasing the allocation alignment requirement to 8 bytes
> (sizeof(u64)) in bpf_jit_binary_pack_alloc(). This anchors the base of
> the JIT buffer to an 8-byte boundary, allowing the relative padding math
> in build_plt() to correctly align the target field.
>
> Fixes: b2ad54e1533e ("bpf, arm64: Implement bpf_arch_text_poke() for arm64")
> Signed-off-by: Fuad Tabba <tabba@google.com>
> ---
> arch/arm64/net/bpf_jit_comp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/net/bpf_jit_comp.c b/arch/arm64/net/bpf_jit_comp.c
> index 356d33c7a4ae..adf84962d579 100644
> --- a/arch/arm64/net/bpf_jit_comp.c
> +++ b/arch/arm64/net/bpf_jit_comp.c
> @@ -2119,7 +2119,7 @@ struct bpf_prog *bpf_int_jit_compile(struct bpf_prog *prog)
> extable_offset = round_up(prog_size + PLT_TARGET_SIZE, extable_align);
> image_size = extable_offset + extable_size;
> ro_header = bpf_jit_binary_pack_alloc(image_size, &ro_image_ptr,
> - sizeof(u32), &header, &image_ptr,
> + sizeof(u64), &header, &image_ptr,
> jit_fill_hole);
> if (!ro_header) {
> prog = orig_prog;
Acked-by: Will Deacon <will@kernel.org>
Will
next prev parent reply other threads:[~2026-02-26 18:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 9:31 [PATCH] arm64: bpf: Fix UBSAN misaligned access in BPF JIT Fuad Tabba
2026-02-25 1:43 ` Xu Kuohai
2026-02-25 9:08 ` Fuad Tabba
2026-02-25 9:46 ` Xu Kuohai
2026-02-25 11:00 ` Fuad Tabba
2026-02-26 1:34 ` Xu Kuohai
2026-02-26 7:55 ` [PATCH v3] arm64: bpf: Force 8-byte alignment for JIT buffer to prevent atomic tearing Fuad Tabba
2026-02-26 18:28 ` Will Deacon [this message]
2026-02-26 19:30 ` patchwork-bot+netdevbpf
2026-02-25 17:47 ` [PATCH] arm64: bpf: Fix UBSAN misaligned access in BPF JIT Will Deacon
2026-02-25 17:53 ` Fuad Tabba
2026-02-25 18:22 ` Will Deacon
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=aaCQ0M9h1QfCPKGb@willie-the-truck \
--to=will@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=jpb@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=puranjay@kernel.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=tabba@google.com \
--cc=xukuohai@huaweicloud.com \
--cc=yonghong.song@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox