CVE-2024-58034 [High] | Use-After-Free in Linux Kernel

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]

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-05-01	0.06%	0.01%	-0.04%
2	2026-04-07	0.03%	0.06%	+0.03%
3	2025-11-21	—	0.03%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-05-01

0.06%

0.01%

-0.04%

2026-04-07

0.03%

0.06%

+0.03%

2025-11-21

—

0.03%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	134c704f-9b21-4f2e-91b3-4a467353bcc0

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

134c704f-9b21-4f2e-91b3-4a467353bcc0

OS Trackers for CVE-2024-58034

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2024-58034 not yet assigned priority: Debian including 2 source packages (linux, linux-6.1), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5, open 1.	https://security-tracker.debian.org/tracker/CVE-2024-58034
`redhat`	high	—	https://access.redhat.com/security/cve/CVE-2024-58034
`suse`	medium	CVE-2024-58034 severity moderate: SUSE including 417 source package names (2.1.3-6.11:kernel-default-6.4.0-28.1, 2.1.3-6.12:kernel-default-base-6.4.0-28.1.21.6, …), 708 product×package rows across 121 product lines (Container suse/sl-micro/6.0/base-os-container, Container suse/sl-micro/6.0/kvm-os-container, … (121 product lines)): Fixed 361, Known Affected 231, Known Not Affected 116.	https://www.suse.com/security/cve/CVE-2024-58034/
`ubuntu`	medium	CVE-2024-58034 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, released 168, ignored 148, not-affected 67, needed 23.	https://ubuntu.com/security/CVE-2024-58034

Affected software / configurations for CVE-2024-58034

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 5.0, < 5.15.179	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 6.1.129	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.2, < 6.6.76	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.7, < 6.12.13	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.13, < 6.13.2	cpe:2.3:o:linux:linux_kernel::::::::

References for CVE-2024-58034

URL	Tags
https://git.kernel.org/stable/c/3b02273446e23961d910b50cc12528faec649fb2	Patch
https://git.kernel.org/stable/c/755e44538c190c31de9090d8e8821d228fcfd416	Patch
https://git.kernel.org/stable/c/b9784e5cde1f9fb83661a70e580e381ae1264d12	Patch
https://git.kernel.org/stable/c/c144423cb07e4e227a8572d5742ca2b36ada770d	Patch
https://git.kernel.org/stable/c/c3def10c610ae046aaa61d00528e7bd15e4ad8d3	Patch
https://git.kernel.org/stable/c/e9d07e91de140679eeaf275f47ad154467cb9e05	Patch
https://lists.debian.org/debian-lts-announce/2025/03/msg00028.html

URL

CVE-2024-58034 | memory: tegra20-emc: fix an OF node reference bug in tegra_emc_find_node_by_ram_code()

Exploit prediction scoring system (EPSS) score for CVE-2024-58034

Common vulnerability scoring system (CVSS) metrics for CVE-2024-58034

Weakness enumeration for CVE-2024-58034

OS Trackers for CVE-2024-58034

Affected software / configurations for CVE-2024-58034

References for CVE-2024-58034