From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Joel Selvaraj <joelselvaraj.oss@gmail.com>
Cc: "srinivas.kandagatla@linaro.org" <srinivas.kandagatla@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ekansh Gupta <quic_ekangupt@quicinc.com>,
stable <stable@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Subject: Re: [PATCH 6/6] misc: fastrpc: Restrict untrusted app to attach to privileged PD
Date: Thu, 15 Aug 2024 12:02:45 +0200 [thread overview]
Message-ID: <2024081531-vision-broadness-daca@gregkh> (raw)
In-Reply-To: <2024081513-aware-tutor-e119@gregkh>
On Thu, Aug 15, 2024 at 10:41:15AM +0200, gregkh@linuxfoundation.org wrote:
> On Thu, Aug 15, 2024 at 03:35:13AM -0500, Joel Selvaraj wrote:
> > Hi greg k-h,
> >
> > The git commit id is: bab2f5e8fd5d2f759db26b78d9db57412888f187
> >
> > But I am bit hesitant if we should revert it because there is a CVE attached
> > to it: https://ubuntu.com/security/CVE-2024-41024
>
> Not an issue if it is breaking things, let's get it right. We can
> trivially reject that CVE if needed.
>
> > Also, I am ok with changing userspace if it's necessary. It would be nice if
> > the authors can clarify the ideal fix here.
>
> No, userspace should not break, that's not ok at all. I'll get someone
> to revert this later today, thanks!
Now sent:
https://lore.kernel.org/r/20240815094920.8242-1-griffin@kroah.com
I'll queue this up later today.
thanks,
greg k-h
next prev parent reply other threads:[~2024-08-15 10:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 11:44 [PATCH 0/6] misc: fastrpc: fixes for 6.10 srinivas.kandagatla
2024-06-28 11:44 ` [PATCH 1/6] misc: fastrpc: Fix DSP capabilities request srinivas.kandagatla
2024-06-28 11:44 ` [PATCH 2/6] misc: fastrpc: Copy the complete capability structure to user srinivas.kandagatla
2024-06-28 11:44 ` [PATCH 3/6] misc: fastrpc: Avoid updating PD type for capability request srinivas.kandagatla
2024-06-28 11:44 ` [PATCH 4/6] misc: fastrpc: Fix memory leak in audio daemon attach operation srinivas.kandagatla
2024-06-28 11:45 ` [PATCH 5/6] misc: fastrpc: Fix ownership reassignment of remote heap srinivas.kandagatla
2024-06-28 11:45 ` [PATCH 6/6] misc: fastrpc: Restrict untrusted app to attach to privileged PD srinivas.kandagatla
2024-08-15 2:34 ` Selvaraj, Joel (MU-Student)
2024-08-15 5:15 ` gregkh
2024-08-15 5:17 ` gregkh
2024-08-15 8:35 ` Joel Selvaraj
2024-08-15 8:41 ` gregkh
2024-08-15 10:02 ` gregkh [this message]
2024-08-15 10:16 ` Joel Selvaraj
2024-08-15 13:30 ` Srinivas Kandagatla
2024-08-15 13:43 ` gregkh
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=2024081531-vision-broadness-daca@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=joelselvaraj.oss@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_ekangupt@quicinc.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=stable@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