Re: [PATCH] Documentation: Document the Linux Kernel CVE process

2024-02-14 Thread Kees Cook
On Wed, Feb 14, 2024 at 08:45:19AM +0100, Greg Kroah-Hartman wrote: > On Wed, Feb 14, 2024 at 07:43:32AM +0100, Greg Kroah-Hartman wrote: > > On Tue, Feb 13, 2024 at 02:35:24PM -0800, Kees Cook wrote: > > > On Tue, Feb 13, 2024 at 07:48:12PM +0100, Greg Kroah-Hartman wrote: > > > > +No CVEs will be

Re: [PATCH] Documentation: Document the Linux Kernel CVE process

2024-02-14 Thread Randy Dunlap
On 2/13/24 23:15, Greg Kroah-Hartman wrote: > On Tue, Feb 13, 2024 at 11:56:42AM -0800, Randy Dunlap wrote: >>> +As part of the normal stable release process, kernel changes that are >>> +potentially security issues are identified by the developers responsible >>> +for CVE number assignments and

Re: [PATCH] Documentation: Document the Linux Kernel CVE process

2024-02-13 Thread Greg Kroah-Hartman
On Wed, Feb 14, 2024 at 07:43:32AM +0100, Greg Kroah-Hartman wrote: > On Tue, Feb 13, 2024 at 02:35:24PM -0800, Kees Cook wrote: > > On Tue, Feb 13, 2024 at 07:48:12PM +0100, Greg Kroah-Hartman wrote: > > > +No CVEs will be assigned for unfixed security issues in the Linux > > > +kernel, assignment

Re: [PATCH] Documentation: Document the Linux Kernel CVE process

2024-02-13 Thread Greg Kroah-Hartman
On Tue, Feb 13, 2024 at 11:56:42AM -0800, Randy Dunlap wrote: > > +As part of the normal stable release process, kernel changes that are > > +potentially security issues are identified by the developers responsible > > +for CVE number assignments and have CVE numbers automatically assigned > > +to

Re: [PATCH] Documentation: Document the Linux Kernel CVE process

2024-02-13 Thread Greg Kroah-Hartman
On Tue, Feb 13, 2024 at 02:35:24PM -0800, Kees Cook wrote: > On Tue, Feb 13, 2024 at 07:48:12PM +0100, Greg Kroah-Hartman wrote: > > +No CVEs will be assigned for unfixed security issues in the Linux > > +kernel, assignment will only happen after a fix is available as it can > > +be properly tracke

Re: [PATCH] Documentation: Document the Linux Kernel CVE process

2024-02-13 Thread Kees Cook
On Tue, Feb 13, 2024 at 07:48:12PM +0100, Greg Kroah-Hartman wrote: > +No CVEs will be assigned for unfixed security issues in the Linux > +kernel, assignment will only happen after a fix is available as it can > +be properly tracked that way by the git commit id of the original fix. This seems at

Re: [PATCH] Documentation: Document the Linux Kernel CVE process

2024-02-13 Thread Randy Dunlap
On 2/13/24 10:48, 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. > > Signed-off-by: Greg Kroah-Hartman > Signe

Re: [PATCH] Documentation: Document the Linux Kernel CVE process

2024-02-13 Thread Jonathan Corbet
Greg Kroah-Hartman writes: > On Tue, Feb 13, 2024 at 07:48:12PM +0100, 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

Re: [PATCH] Documentation: Document the Linux Kernel CVE process

2024-02-13 Thread Greg Kroah-Hartman
On Tue, Feb 13, 2024 at 07:48:12PM +0100, 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. > > Signed-off-by: Greg K