From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "James Burton" <jamesburton@meta.com>
Cc: "bpf" <bpf@vger.kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Eduard" <eddyz87@gmail.com>,
"Anton Protopopov" <a.s.protopopov@gmail.com>,
"Greg KH" <gregkh@linuxfoundation.org>
Subject: Re: gotox/INSN_ARRAY cross-subprog fixes: request vuln-fix designation and stable tags
Date: Sun, 01 Nov 2026 01:33:43 +0000 [thread overview]
Message-ID: <DMJHKAHV1KRA.OV1LITSNYP3D@gmail.com> (raw)
In-Reply-To: <CAJgm7qMEz-O1+L2MJz+qqH6-pz_ELaQNG0QQkgMbHOoDi69R4Q@mail.gmail.com>
On Sat Oct 31, 2026 at 11:07 PM UTC, James Burton wrote:
> Daniel, Alexei,
>
> Fair enough on searching lore first. I did, and that's actually what
> prompted the question.
>
> The same gotox/insn_array feature already has three fixes that only
> needed CAP_BPF and still got CVEs and stable backports:
>
> - CVE-2026-43321, mark live registers for indirect jumps, in 6.19.6 and 7.0
> - CVE-2026-93043, interpreter fallback BUG_ON for gotox, in 7.2.6 and 7.3
> - CVE-2026-45967, wrong address for insn array offsets, in 6.19.4 and 7.0
>
> The two I reported, 19581372dd81 and c48a91c049fd, look like the same
> kind of bug on that feature and sit behind the same CAP_BPF gate, but
> they're mainline only, so 6.19 through 7.3 still carry them. The first
> one has a deterministic reproducer that goes from CAP_BPF to root.
Are you after cve scorecard or you want to truly improve kernel security?
If later then please skip all bugs that need cap_*.
next prev parent reply other threads:[~2026-11-01 1:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJgm7qNx6NBzfxQbwF0ZoMLoULquNpsnrYSL1F3EFf2tztES7Q@mail.gmail.com>
2026-10-30 22:39 ` gotox/INSN_ARRAY cross-subprog fixes: request vuln-fix designation and stable tags Greg KH
2026-10-31 1:10 ` James Burton
2026-10-31 5:26 ` Alexei Starovoitov
2026-10-31 23:07 ` James Burton
2026-11-01 1:33 ` Alexei Starovoitov [this message]
2026-11-01 7:26 ` James Burton
2026-11-01 13:07 ` Greg KH
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=DMJHKAHV1KRA.OV1LITSNYP3D@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=a.s.protopopov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jamesburton@meta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.