[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025081653-CVE-2025-38518-2b55@gregkh>
Date: Sat, 16 Aug 2025 12:58:00 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38518: x86/CPU/AMD: Disable INVLPGB on Zen2
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
x86/CPU/AMD: Disable INVLPGB on Zen2
AMD Cyan Skillfish (Family 17h, Model 47h, Stepping 0h) has an issue
that causes system oopses and panics when performing TLB flush using
INVLPGB.
However, the problem is that that machine has misconfigured CPUID and
should not report the INVLPGB bit in the first place. So zap the
kernel's representation of the flag so that nothing gets confused.
[ bp: Massage. ]
The Linux kernel CVE team has assigned CVE-2025-38518 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.15 with commit 767ae437a32d644786c0779d0d54492ff9cbe574 and fixed in 6.15.7 with commit 357f121517924e3ec3021f9d0dd0189adcd09867
Issue introduced in 6.15 with commit 767ae437a32d644786c0779d0d54492ff9cbe574 and fixed in 6.16 with commit a74bb5f202dabddfea96abc1328fcedae8aa140a
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2025-38518
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
arch/x86/kernel/cpu/amd.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/357f121517924e3ec3021f9d0dd0189adcd09867
https://git.kernel.org/stable/c/a74bb5f202dabddfea96abc1328fcedae8aa140a
Powered by blists - more mailing lists