From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jesper Dangaard Brouer <hawk@kernel.org>,
Andrey Ignatov <rdna@fb.com>
Cc: Sasha Levin <sashal@kernel.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, Yinhao Hu <dddddd@hust.edu.cn>,
Kaiyan Mei <M202472210@hust.edu.cn>,
Dongliang Mu <dzm91@hust.edu.cn>,
"Miguel Gazquez (Schneider Electric)"
<miguel.gazquez@bootlin.com>
Subject: Re: [PATCH 5.15.y] bpf: Enforce expected_attach_type for tailcall compatibility
Date: Fri, 11 Sep 2026 07:20:54 -0400 [thread overview]
Message-ID: <daily-reply-0035-re-bpf-tailcall-5-15@kernel.org> (raw)
In-Reply-To: <20260910-cve-2025-40123-5-15-v1-1-547774d4a00b@bootlin.com>
> [ Upstream commit 4540aed51b12bc13364149bf95f6ecef013197c0 ]
>
> Yinhao et al. recently reported:
>
> Our fuzzer tool discovered an uninitialized pointer issue in the
> bpf_prog_test_run_xdp() function within the Linux kernel's BPF
> subsystem.
Queued for 5.15, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-09-11 11:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 9:33 [PATCH 5.15.y] bpf: Enforce expected_attach_type for tailcall compatibility Miguel Gazquez (Schneider Electric)
2026-09-11 11:20 ` Sasha Levin [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=daily-reply-0035-re-bpf-tailcall-5-15@kernel.org \
--to=sashal@kernel.org \
--cc=M202472210@hust.edu.cn \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dddddd@hust.edu.cn \
--cc=dzm91@hust.edu.cn \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.gazquez@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=rdna@fb.com \
--cc=songliubraving@fb.com \
--cc=stable@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yhs@fb.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