[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <75f89fc2-4b43-4311-bc84-03738dead5cc@kernel.org>
Date: Wed, 14 Feb 2024 14:10:07 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, corbet@....net,
workflows@...r.kernel.org
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
security@...nel.org, Kees Cook <keescook@...omium.org>,
Sasha Levin <sashal@...nel.org>, Lee Jones <lee@...nel.org>
Subject: Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
On 14/02/2024 09:00, Greg Kroah-Hartman wrote:
> The Linux kernel project now has the ability to assign CVEs to fixed
> issues, so document the process and how individual developers can get a
> CVE if one is not automatically assigned for their fixes.
>
> Reviewed-by: Kees Cook <keescook@...omium.org>
> Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Signed-off-by: Sasha Levin <sashal@...nel.org>
> Signed-off-by: Lee Jones <lee@...nel.org>
> ---
> v3: fix up wording in security-bugs.rst based on the changes to the cve
> assignment process from v1, thanks to a private reviewer for
> pointing that out.
> v2: Grammer fixes based on review from Randy
> Updated paragraph about how CVE identifiers will be assigned
> (automatically when added to stable trees, or ask us for one
> directly before that happens if so desired)
>
> Documentation/process/cve.rst | 120 ++++++++++++++++++++++++
> Documentation/process/index.rst | 1 +
> Documentation/process/security-bugs.rst | 5 +-
Great direction! Finally all these bugs we are fixing every release
(thus in stable trees) will get proper attention via assigned CVEs.
Reviewed-by: Krzysztof Kozlowski <krzk@...nel.org>
Best regards,
Krzysztof
Powered by blists - more mailing lists