linux-kernel - Re: CVE-2024-26650: platform/x86: p2sb: Allow p2sb

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZlBs8u8M5US5aAro@tiehlicka>
Date: Fri, 24 May 2024 12:33:22 +0200
From: Michal Hocko <mhocko@...e.com>
To: cve@...nel.org, linux-kernel@...r.kernel.org
Cc: linux-cve-announce@...r.kernel.org, Lee Jones <lee@...nel.org>
Subject: Re: CVE-2024-26650: platform/x86: p2sb: Allow p2sb_bar() calls
 during PCI device probe

On Tue 21-05-24 21:31:54, Michal Hocko wrote:
> 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.

Wait a second. I've screwed up here. I am sorry, my bad. This revert has
nothing to do with CVE-2024-26650 - 5913320eb0b3 ("platform/x86: p2sb:
Allow p2sb_bar() calls during PCI device probe"). I guess I got
completely confused by the fact that the same change exists under a
different commit b28ff7a7c324 ("platform/x86: p2sb: Allow p2sb_bar()
calls during PCI device probe").

I must have mixed this with CVE-2024-35928 somehow. zhengzucheng has
already pointed to that one. Sorry about that!

-- 
Michal Hocko
SUSE Labs