linux-cve-announce - CVE-2024-58034: memory: tegra20-emc: fix an OF node reference bug in tegra_emc_find_node_by_ram

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025022751-CVE-2024-58034-36fb@gregkh>
Date: Thu, 27 Feb 2025 11:59:50 -0800
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-58034: memory: tegra20-emc: fix an OF node reference bug in tegra_emc_find_node_by_ram_code()

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

memory: tegra20-emc: fix an OF node reference bug in tegra_emc_find_node_by_ram_code()

As of_find_node_by_name() release the reference of the argument device
node, tegra_emc_find_node_by_ram_code() releases some device nodes while
still in use, resulting in possible UAFs. According to the bindings and
the in-tree DTS files, the "emc-tables" node is always device's child
node with the property "nvidia,use-ram-code", and the "lpddr2" node is a
child of the "emc-tables" node. Thus utilize the
for_each_child_of_node() macro and of_get_child_by_name() instead of
of_find_node_by_name() to simplify the code.

This bug was found by an experimental verification tool that I am
developing.

[krzysztof: applied v1, adjust the commit msg to incorporate v2 parts]

The Linux kernel CVE team has assigned CVE-2024-58034 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.0 with commit 96e5da7c842424bcf64afe1082b960b42b96190b and fixed in 6.1.129 with commit e9d07e91de140679eeaf275f47ad154467cb9e05
	Issue introduced in 5.0 with commit 96e5da7c842424bcf64afe1082b960b42b96190b and fixed in 6.6.76 with commit c144423cb07e4e227a8572d5742ca2b36ada770d
	Issue introduced in 5.0 with commit 96e5da7c842424bcf64afe1082b960b42b96190b and fixed in 6.12.13 with commit 3b02273446e23961d910b50cc12528faec649fb2
	Issue introduced in 5.0 with commit 96e5da7c842424bcf64afe1082b960b42b96190b and fixed in 6.13.2 with commit 755e44538c190c31de9090d8e8821d228fcfd416
	Issue introduced in 5.0 with commit 96e5da7c842424bcf64afe1082b960b42b96190b and fixed in 6.14-rc1 with commit b9784e5cde1f9fb83661a70e580e381ae1264d12

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-58034
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:
	drivers/memory/tegra/tegra20-emc.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/e9d07e91de140679eeaf275f47ad154467cb9e05
	https://git.kernel.org/stable/c/c144423cb07e4e227a8572d5742ca2b36ada770d
	https://git.kernel.org/stable/c/3b02273446e23961d910b50cc12528faec649fb2
	https://git.kernel.org/stable/c/755e44538c190c31de9090d8e8821d228fcfd416
	https://git.kernel.org/stable/c/b9784e5cde1f9fb83661a70e580e381ae1264d12