ACPICA: Refuse to evaluate a method if arguments are missing
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 18ff4ed6a33a7e3f2097710eacc96bea7696e803| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
ACPICA in the Linux kernel can crash from a use-after-free when a firmware method is called with fewer arguments than it expects. The reported case followed a platform firmware update that changed the method’s parameter count without updating a caller; the input does not describe an attacker path, authentication requirements, or user interaction.
Engineers running Linux kernels on systems with affected platform firmware should check their deployments; affected versions are not specified.