From: Greg KH <gregkh@linuxfoundation.org>
To: Hardik Gohil <hgohil@mvista.com>
Cc: stable@vger.kernel.org
Subject: Re: Attaching CVE-ID to specific kernel fixes
Date: Fri, 11 Sep 2026 13:30:01 +0200 [thread overview]
Message-ID: <2026091145-trilogy-raider-b6cb@gregkh> (raw)
In-Reply-To: <CAH+zgeGSQTgn=LVUKj-T4LnxSFjn-t7cftfAiEvAsQpdr9sfXg@mail.gmail.com>
On Fri, Sep 11, 2026 at 04:50:40PM +0530, Hardik Gohil wrote:
> Hello Greg,
>
> I had a query regarding CVE fixes for LTS kernels. I noticed that
> while fixes are backported to LTS kernels, the corresponding CVE ID is
> sometimes not included in the patch.
Yes, because it's not needed.
> May I know the reason for not adding the CVE ID to these fixes?
We just keep the identical changelog from what is in mainline.
> Wouldn’t it be a good practice to include the CVE ID in the patch, as
> it would make it easier to identify and track the security fixes?
That's not what the kernel changelog is for, that is what the kernel cve
vulns.git repo is for. Some CVE ids change over time, and some are
rejected and the like. To attempt to keep that all up to date in the
kernel source tree itself without rewriting history would be impossible.
thanks,
greg k-h
prev parent reply other threads:[~2026-09-11 11:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 11:20 Attaching CVE-ID to specific kernel fixes Hardik Gohil
2026-09-11 11:30 ` 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=2026091145-trilogy-raider-b6cb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hgohil@mvista.com \
--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