ACPI: custom_method: fix potential use-after-free issue
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 03d1571d9513369c17e6848476763ebbd10ec2cb · < 62dc2440ebb552aa0d7f635e1697e077d9d21203| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ACPI: custom_method: fix potential use-after-free issue
In cm_write(), buf is always freed when reaching the end of the function. If the requested count is less than table.length, the allocated buffer will be freed but subsequent calls to cm_write() will still try to access it.
Remove the unconditional kfree(buf) at the end of the function and set the buf to NULL in the -EINVAL error path to match the rest of function.
From the CVE record · Linux
The Linux kernel's ACPI custom_method cm_write() can free a buffer when the requested count is less than table.length, then access it on subsequent calls. This creates a potential use-after-free; the input does not specify whether exploitation requires local or network access, authentication, or user interaction.
Engineers running the Linux kernel should check their versions; affected versions are not specified.