[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <725225922c8c85861861f794b6386d450d67d26c.camel@oracle.com>
Date: Wed, 24 Jul 2024 10:19:19 +0000
From: Siddh Raman Pant <siddh.raman.pant@...cle.com>
To: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
CC: "cve@...nel.org" <cve@...nel.org>,
"linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>
Subject: Re: CVE-2024-39471: drm/amdgpu: add error handle to avoid
out-of-bounds
On Wed, Jul 24 2024 at 15:44:12 +0530, gregkh@...uxfoundation.org
wrote:
> On Wed, Jul 24, 2024 at 10:05:53AM +0000, Siddh Raman Pant wrote:
> > On Tue, 25 Jun 2024 16:29:04 +0200, Greg Kroah-Hartman wrote:
> > > In the Linux kernel, the following vulnerability has been resolved:
> > >
> > > drm/amdgpu: add error handle to avoid out-of-bounds
> > >
> > > if the sdma_v4_0_irq_id_to_seq return -EINVAL, the process should
> > > be stop to avoid out-of-bounds read, so directly return -EINVAL.
> > >
> > > The Linux kernel CVE team has assigned CVE-2024-39471 to this issue.
> >
> > This commit has a bug which was fixed by 6769a23697f1. It should be
> > immediately backported, otherwise this "fix" doesn't do anything since
> > gcc will optimise out the check.
>
> <formletter>
>
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree. Please read:
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> for how to do this properly.
>
> </formletter>
>
> (hint, send the request to stable@...r.kernel.org, not
> cve@...nel.org...)
>
> Also, any specific reason why that commit was NOT marked for stable
> inclusion by the developers/maintainers involved with it and you didn't
> cc any of them here either :(
Oops, sorry, my bad.
Siddh
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists