LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22047: x86/microcode/AMD: Fix __apply_microcode_amd()'s return value

In the Linux kernel, the following vulnerability has been resolved: x86/microcode/AMD: Fix __apply_microcode_amd()'s return value When verify_sha256_digest() fails, __apply_microcode_amd() should propagate the failure by returning false (and not -1 which is promoted to true).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects AMD microcode update handling. A failed SHA-256 verification could be reported as success because a negative return value was treated as true. The business risk is unclear from the supplied sources because no CVSS score, attack scenario, or active exploitation evidence is provided.

Executive priority

Track and patch through normal kernel maintenance unless vendor guidance raises severity. Escalate for fleets with AMD servers where kernel or microcode update integrity is operationally important.

Technical view

In x86/microcode/AMD, __apply_microcode_amd() returned -1 when verify_sha256_digest() failed. Because the caller expected a boolean, -1 could be promoted to true, masking the failed verification. The fix is to return false on digest verification failure.

Likely exposure

Potential exposure is limited to Linux systems using the AMD microcode update path in affected kernel builds identified by the CVE record. The supplied affected-version data is not enough to map every distribution package reliably, so kernel vendor advisories should be checked.

Exploitation context

The source bundle does not show CISA KEV listing, active exploitation, public exploit use, or a complete attack path. It describes a kernel correctness flaw in error propagation during AMD microcode verification, not a confirmed remotely exploitable vulnerability.

Researcher notes

Evidence is narrow: the CVE record and kernel commits identify a boolean return-value bug in AMD microcode digest verification handling. They do not provide CVSS, CWE, exploitability details, or distribution-specific package mappings.

Mitigation direction

  • Update to a vendor Linux kernel containing the linked stable fixes.
  • Prioritize AMD-based Linux hosts that load CPU microcode through the kernel.
  • Check distribution advisories for exact fixed package versions.
  • Follow vendor guidance if fixed packages are not yet available.

Validation and detection

  • Inventory Linux kernel versions across AMD-based systems.
  • Confirm whether installed kernels include the referenced stable commits.
  • Review vendor security advisories for CVE-2025-22047 package status.
  • After updating, verify hosts boot the expected fixed kernel.
Prepared
Confidence
medium
Sources
7

Public sources used

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-22047 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxbef830144febedb7de86863ae99d8f53bed76e95, 3e8653e399e7111a3e87d534ff4533b250ae574f, c162ba4f45ab6ef3b7114af6fb419f1833f050c0, 50cef76d5cb0e199cda19f026842560f6eedc4f7, 50cef76d5cb0e199cda19f026842560f6eedc4f7, 6.6.81, 6.12.18, 6.13.6unaffected
LinuxLinux6.14, 0, 6.6.87, 6.12.23, 6.13.11, 6.14.2, 6.15affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.