From: Greg KH <gregkh@linuxfoundation.org>
To: Nakashima Seiichi <s-nakashima@kjb.biglobe.ne.jp>
Cc: kernel-hardening@lists.openwall.com,
linux-security-module@vger.kernel.org
Subject: Re: [Case Study] CVE-2024-0582: Why We Need a Standard for CVE Emergency Mitigation
Date: Tue, 10 Nov 2026 16:52:41 -0500 [thread overview]
Message-ID: <2026111052-spectator-legwarmer-4c1e@gregkh> (raw)
In-Reply-To: <1d9ab7140a015e94829e2356a4c6c9e18d92b864.camel@kjb.biglobe.ne.jp>
On Wed, Nov 11, 2026 at 06:28:39AM +0900, Nakashima Seiichi wrote:
> The case study demonstrates the gap between "technically possible"
> and "operationally scalable." With a standardized framework, the
> mitigation could have started on CVE publication day instead of
> waiting ~2.5 months for the distro patch.
There was a working patch before the CVE was issued, so who is waiting 2
1/2 months for anything?
Also, remember we are issuing about 55 CVEs per day right now, who is
going to do all of this review and "mitigation" for all of those
entries? That's almost 2 per hour, 24 hours a day. Do you have the
free tokens to burn on that?
And again, why? You have a fix. Given to you for free. Just apply it.
good luck!
greg k-h
prev parent reply other threads:[~2026-11-10 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1d9ab7140a015e94829e2356a4c6c9e18d92b864.camel@kjb.biglobe.ne.jp>
2026-11-10 21:10 ` [Case Study] CVE-2024-0582: Why We Need a Standard for CVE Emergency Mitigation Marian Marinov
2026-11-10 21:52 ` Greg KH [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=2026111052-spectator-legwarmer-4c1e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-security-module@vger.kernel.org \
--cc=s-nakashima@kjb.biglobe.ne.jp \
/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