LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38386: ACPICA: Refuse to evaluate a method if arguments are missing

In the Linux kernel, the following vulnerability has been resolved: ACPICA: Refuse to evaluate a method if arguments are missing As reported in [1], a platform firmware update that increased the number of method parameters and forgot to update a least one of its callers, caused ACPICA to crash due to use-after-free. Since this a result of a clear AML issue that arguably cannot be fixed up by the interpreter (it cannot produce missing data out of thin air), address it by making ACPICA refuse to evaluate a method if the caller attempts to pass fewer arguments than expected to it.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux ACPI interpreter flaw can cause a use-after-free when faulty firmware calls an AML method without all required arguments. The reported outcome is a kernel crash. The CVSS assessment indicates potentially broader confidentiality, integrity, and availability impact, but the supplied evidence does not confirm those outcomes.

Executive priority

Treat as a high-priority maintenance issue, especially for multi-user Linux fleets or systems recently receiving firmware updates. Accelerate normal kernel patching and investigate affected hardware, but current evidence does not justify an emergency response based on active exploitation.

Technical view

ACPICA previously evaluated AML methods even when callers supplied fewer arguments than declared. A firmware update introduced such a mismatch, leading to use-after-free. The Linux fix rejects method evaluation when required arguments are missing. CVSS 3.1 is 7.8, requiring local access and low privileges, with no user interaction.

Likely exposure

Exposure applies to Linux systems running affected kernels where platform firmware contains or introduces the malformed AML call pattern. Practical reachability is hardware- and firmware-dependent. The supplied version data is ambiguous, so organizations should validate distribution kernel packages and backports rather than relying only on upstream version numbers.

Exploitation context

CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public exploit. The documented trigger was a defective platform firmware update. CVSS classifies attack access as local with low privileges, but the bundle confirms a crash rather than demonstrated privilege escalation or code execution.

Researcher notes

The security boundary and reliable trigger conditions remain incompletely documented in the supplied material. Analysis should distinguish upstream versions from distribution backports and correlate failures with firmware AML changes. The fix is defensive argument-count validation; the underlying firmware defect may remain. Avoid inferring arbitrary code execution from the use-after-free without additional evidence.

Mitigation direction

  • Install distribution or vendor kernel updates containing the referenced ACPICA fix.
  • Confirm custom kernels include the applicable stable-branch patch or an equivalent backport.
  • Review hardware-vendor guidance for firmware versions containing malformed AML method calls.
  • Prioritize exposed multi-user systems while assessing firmware-specific reachability.

Validation and detection

  • Inventory running kernel versions, distribution package revisions, hardware models, and firmware versions.
  • Verify the installed kernel package documents CVE-2025-38386 remediation or includes an equivalent backport.
  • Check kernel and crash logs for ACPICA failures or use-after-free reports following firmware updates.
  • Test applicable firmware and patched kernels in staging before broad deployment.
Prepared
Confidence
high
Sources
6

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-38386 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
1ADP providers
11Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-38386Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2unaffected
LinuxLinux2.6.12, 0, 5.4.296, 5.10.240, 5.15.187, 6.1.144, 6.6.97, 6.12.37, 6.15.6, 6.16affected
Weakness

CWE details

No CWE listed

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