From: Greg KH <gregkh@linuxfoundation.org>
To: hsimeliere.opensource@witekio.com
Cc: andrii@kernel.org, ast@kernel.org, bruno.vernay@se.com,
stable@vger.kernel.org, xukuohai@huawei.com
Subject: Re: [PATCH v2 6.1] bpf: Prevent tail call between progs attached to different hooks
Date: Mon, 10 Feb 2025 10:55:07 +0100 [thread overview]
Message-ID: <2025021027-repaying-purveyor-9744@gregkh> (raw)
In-Reply-To: <20250210094407.209620-1-hsimeliere.opensource@witekio.com>
On Mon, Feb 10, 2025 at 10:44:07AM +0100, hsimeliere.opensource@witekio.com wrote:
> This patch is needed to correct CVE-2024-50063
What patch? I see no context here :(
> https://nvd.nist.gov/vuln/detail/CVE-2024-50063
Never link to nvd, their "enhancements" are provably wrong and hurtful
to the kernel ecosystem. Always just refer to cve.org records or better
yet, our own announcements.
That being said, why do you feel this commit is really needed in those
older kernels other than just trying to meet a "check box" requirement
somewhere?
thanks,
greg k-h
next prev parent reply other threads:[~2025-02-10 9:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 8:40 [PATCH 6.1] bpf: Prevent tail call between progs attached to different hooks hsimeliere.opensource
2025-01-10 17:39 ` Sasha Levin
2025-01-12 11:51 ` Greg KH
2025-01-21 15:41 ` [PATCH v2 " hsimeliere.opensource
2025-01-21 17:09 ` Greg KH
2025-02-10 9:44 ` hsimeliere.opensource
2025-02-10 9:55 ` Greg KH [this message]
2025-02-10 14:29 ` hsimeliere.opensource
2025-02-10 14:43 ` Greg KH
2025-02-10 16:32 ` hsimeliere.opensource
2025-02-11 6:41 ` Greg KH
2025-01-21 19:52 ` Sasha Levin
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=2025021027-repaying-purveyor-9744@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bruno.vernay@se.com \
--cc=hsimeliere.opensource@witekio.com \
--cc=stable@vger.kernel.org \
--cc=xukuohai@huawei.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