[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024111924-CVE-2024-53075-2e34@gregkh>
Date: Tue, 19 Nov 2024 18:31:26 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-53075: riscv: Prevent a bad reference count on CPU nodes
Description
===========
In 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.
The Linux kernel CVE team has assigned CVE-2024-53075 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.11 with commit 604f32ea6909 and fixed in 6.11.7 with commit 303846a3dc27
Issue introduced in 6.11 with commit 604f32ea6909 and fixed in 6.12 with commit 37233169a6ea
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2024-53075
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
arch/riscv/kernel/cacheinfo.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/303846a3dc275e35fbb556d72f1e356ba669e4f8
https://git.kernel.org/stable/c/37233169a6ea912020c572f870075a63293b786a
Powered by blists - more mailing lists