CVE-2025-38518: x86/CPU/AMD: Disable INVLPGB on Zen2
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. ]
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects a narrow AMD Zen2 platform where the CPU incorrectly advertises INVLPGB support. When the kernel uses that feature for TLB flushing, the system can crash with oopses or panics. The main business risk is availability disruption on affected hosts, not confirmed data compromise.
Executive priority
Treat this as a targeted availability-risk patch, not a broad emergency. Prioritize systems matching the AMD hardware and affected Linux kernel versions, especially production hosts where unexpected panics would cause customer or operational impact.
Technical view
The fix clears the kernel’s INVLPGB capability representation for AMD Cyan Skillfish, Family 17h Model 47h Stepping 0h. The root issue is misconfigured CPUID reporting, causing unsafe use of INVLPGB during TLB flush operations. Public data lists Linux kernel 6.15 through before 6.15.7 and 6.16 as affected.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions on the specified AMD Cyan Skillfish Zen2 CPU stepping. Organizations without that hardware or without affected kernel builds are less likely to be exposed based on the provided sources.
Exploitation context
No active exploitation is supported by the supplied sources, and the CVE is not listed as KEV. The described failure mode is system oops or panic during kernel TLB flush behavior, so exploitation context is availability impact rather than a documented remote attack path.
Researcher notes
The public record provides a concise kernel fix rationale but no CVSS, CWE, exploit details, or broad product matrix. Analysis should stay anchored to the specific CPUID/INVLPGB mismatch and the named AMD Cyan Skillfish CPU identification.
Mitigation direction
Apply a Linux kernel update containing the referenced stable fix.
Use distribution vendor kernels with the CVE backport where available.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38518 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Aug 16, 2025, 10:55 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.