From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Siddh Raman Pant <siddh.raman.pant@oracle.com>
Cc: "cve@kernel.org" <cve@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: CVE-2024-39471: drm/amdgpu: add error handle to avoid out-of-bounds
Date: Wed, 24 Jul 2024 12:14:12 +0200 [thread overview]
Message-ID: <2024072457-citrus-shortness-c3e5@gregkh> (raw)
In-Reply-To: <d5e6930140e85c92e7ab4b7d68642d754ead1746.camel@oracle.com>
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@vger.kernel.org, not
cve@kernel.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 :(
thanks,
greg k-h
next prev parent reply other threads:[~2024-07-24 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024062501-CVE-2024-39471-3dee@gregkh>
2024-07-24 10:05 ` Siddh Raman Pant
2024-07-24 10:14 ` gregkh [this message]
2024-07-24 10:19 ` Siddh Raman Pant
2024-07-24 10:24 ` Siddh Raman Pant
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=2024072457-citrus-shortness-c3e5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=siddh.raman.pant@oracle.com \
/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
all inboxes | Powered by JetHome®