From: Greg KH <gregkh@linuxfoundation.org>
To: zhengzucheng <zhengzucheng@huawei.com>
Cc: Michal Hocko <mhocko@suse.com>,
linux-cve-announce@vger.kernel.org, Lee Jones <lee@kernel.org>,
Jun.Ma2@amd.com, cve@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: CVE-2024-26650: platform/x86: p2sb: Allow p2sb_bar() calls during PCI device probe
Date: Thu, 23 May 2024 15:51:38 +0200 [thread overview]
Message-ID: <2024052316-subtotal-fragrance-15e3@gregkh> (raw)
In-Reply-To: <da7e8c85-52fd-b2f4-83da-751f812de6ae@huawei.com>
On Thu, May 23, 2024 at 04:50:18PM +0800, zhengzucheng wrote:
>
> 在 2024/5/22 3:31, Michal Hocko 写道:
> > This patch has been reverted in upstream by 03c6284df179 ("Revert
> > "drm/amd/amdgpu: Fix potential ioremap() memory leaks in
> > amdgpu_device_init()"") and based on the changelog the CVE should be
> > rejected.
>
> hi Michal Hocko
>
> This reverted patch was previously used to resolve CVE-2024-35928 ?
>
> so CVE-2024-35928 should be rejected?
>
>
> commit 03c6284df179de3a4a6e0684764b1c71d2a405e2
> Author: Ma Jun <Jun.Ma2@amd.com>
> Date: Tue Mar 19 15:24:03 2024 +0800
>
> Revert "drm/amd/amdgpu: Fix potential ioremap() memory leaks in
> amdgpu_device_init()"
>
> This patch causes the following iounmap erorr and calltrace
> iounmap: bad address 00000000d0b3631f
>
> The original patch was unjustified because amdgpu_device_fini_sw() will
> always cleanup the rmmio mapping.
>
> This reverts commit eb4f139888f636614dab3bcce97ff61cefc4b3a7.
>
> Signed-off-by: Ma Jun <Jun.Ma2@amd.com>
> Suggested-by: Christian König <christian.koenig@amd.com>
> Reviewed-by: Christian König <christian.koenig@amd.com>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Yes, this should be rejected, I'll go do that now, thanks for pointing
out the revert, we missed that.
greg k-h
next prev parent reply other threads:[~2024-05-23 13:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240326175007.1388794-18-lee@kernel.org>
2024-05-21 19:31 ` Michal Hocko
2024-05-22 4:10 ` Greg KH
2024-05-23 8:50 ` zhengzucheng
2024-05-23 13:51 ` Greg KH [this message]
2024-05-24 10:33 ` Michal Hocko
2024-05-24 10:33 ` Michal Hocko
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=2024052316-subtotal-fragrance-15e3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Jun.Ma2@amd.com \
--cc=cve@kernel.org \
--cc=lee@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=zhengzucheng@huawei.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®