riscv: Prevent a bad reference count on CPU nodes
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.11.76.12In the Linux kernel, the following vulnerability has been resolved:
riscv: Prevent a bad reference count on CPU nodes
When populating cache leaves we previously fetched the CPU device node at the very beginning. But when ACPI is enabled we go through a specific branch which returns early and does not call 'of_node_put' for the node that was acquired.
Since we are not using a CPU device node for the ACPI code anyways, we can simply move the initialization of it just passed the ACPI block, and we are guaranteed to have an 'of_node_put' call for the acquired node. This prevents a bad reference count of the CPU device node.
Moreover, the previous function did not check for errors when acquiring the device node, so a return -ENOENT has been added for that case.
From the CVE record · Linux
The Linux kernel’s RISC-V cache leaf population code can leave a CPU device node reference unreleased when ACPI is enabled. This causes a bad reference count; the input does not describe an attacker action or specify access or user-interaction requirements.
Engineers running Linux kernels with RISC-V and ACPI enabled should check their kernel versions; affected versions were not provided.