Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Joseph Salisbury <joseph.salisbury@oracle.com>
Cc: sashal@kernel.org,
	Ramanan Govindarajan <ramanan.govindarajan@oracle.com>,
	stable@vger.kernel.org
Subject: Re: Confirmation on EOL for Linux 5.4 Stable Kernel
Date: Thu, 25 Sep 2025 08:29:58 +0200	[thread overview]
Message-ID: <2025092524-tree-reproach-7e99@gregkh> (raw)
In-Reply-To: <df5cf0f2-55c6-4786-b129-0a84101a5801@oracle.com>

On Wed, Sep 24, 2025 at 04:01:08PM -0400, Joseph Salisbury wrote:
> 
> 
> On 9/24/25 13:41, Joseph Salisbury wrote:
> > Hi Greg/Sasha,
> > 
> > I am reaching out to confirm the projected EOL for the Linux 5.4 stable
> > kernel.
> > 
> > According to the information listed on kernel.org [0], the EOL is
> > currently slated for December 2025. We are using this projection for
> > planning, so we would be grateful if you could confirm it is still
> > accurate.
> > 
> > Thank you very much for your time and for all the work you do in
> > maintaining the stable kernel releases!
> > 
> > Thanks,
> > 
> > Joe Salisbury
> > 
> > 
> > [0] https://www.kernel.org/category/releases.html
> 
> Sorry, I forgot to CC stable for the wider audience.  Doing that now.

Yes, 5.4 will be going end-of-life in December.  Right now, with the
5.4.299 kernel release, I count 1419 unfixed CVEs in that release, which
does NOT include the known CPU vulnerabilities that are not fixed in
that branch as well (kernel.org does not assign CPU bug CVEs).

So if I were to just go off of that number, I would think that this was
already an "unsupported" kernel tree, and would never recommend anyone
use it for anything that is exposed to untrusted users.

Anyway, I understand that's not the business model you all are in, and I
wish you the best of luck maintaining that beast for longer periods of
time.  Hopefully people are throwing large buckets of cash at you to do
so :)

thanks,

greg k-h

      reply	other threads:[~2025-09-25  6:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7502ef4f-a911-4c08-bdfc-eb17183e668e@oracle.com>
2025-09-24 20:01 ` Confirmation on EOL for Linux 5.4 Stable Kernel Joseph Salisbury
2025-09-25  6:29   ` 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=2025092524-tree-reproach-7e99@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=joseph.salisbury@oracle.com \
    --cc=ramanan.govindarajan@oracle.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    /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