high CVSS 7.8

CVE-2024-58034·Kernel vulnerability

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]

Severity
high
Software
Kernel
Fixed in
6.13.2
Published
2025-02-27

Affected versions

From: 6.13

Until: 6.13.2

Fixed in: 6.13.2

How to fix this CVE

Update your Linux kernel to version 6.13.2 or later to resolve a use-after-free vulnerability in the Tegra20 EMC memory driver. This vulnerability stems from improper device node reference handling during memory table initialization. Kernel updates should be applied promptly to prevent potential system crashes or privilege escalation through the affected memory management subsystem.

sudo dnf update kernel kernel-devel

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check your kernel version with `uname -r` and compare against 6.13.2 — versions 6.13 through 6.13.1 are vulnerable
  2. Step 2: Verify if Tegra20 EMC driver is loaded on your system using `lsmod | grep tegra_emc`
  3. Step 3: Search system logs for UAF-related crashes: `sudo journalctl -xe | grep -i 'use-after-free\|use after free\|double free'`
  4. Step 4: After patching, reboot your system and confirm the new kernel version with `uname -r` to verify the fix is active

FAQ

What is CVE-2024-58034?

CVE-2024-58034 is a use-after-free vulnerability in the Linux kernel's Tegra20 EMC (external memory controller) driver where device node references are incorrectly released during memory table enumeration, potentially allowing local privilege escalation.

Is CVE-2024-58034 being actively exploited?

No, there is no evidence of active exploitation in the wild, and no public exploit code is currently available. This is a local kernel vulnerability requiring prior system access.

What versions of Kernel are affected by CVE-2024-58034?

Linux kernel versions 6.13, 6.13.1, and earlier 6.13.x releases prior to 6.13.2 are affected. Systems running kernel 6.13.2 or later are not vulnerable.

How do I check if my server is vulnerable to CVE-2024-58034?

Run `uname -r` to display your kernel version. If it shows 6.13.0 or 6.13.1, your system is vulnerable. Additionally, check if the Tegra20 EMC driver is present with `grep -r tegra_emc /lib/modules/$(uname -r)/`.

Does Defensia detect CVE-2024-58034?

Yes — Defensia's CVE advisory scanner compares installed kernel package versions against the NVD database. If a vulnerable kernel version is detected on a monitored server, CVE-2024-58034 will appear in your dashboard with remediation steps and patch availability.

Related Kernel CVEs

CVE-2024-42256CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: cifs: Fix server re-repick on subrequest retry When a subrequest is marked for needing retry, netfs will call cifs_prepare_write() which will make cifs repick the server for the op before renegotiating credits; it then calls cifs_issue_write() which invokes smb2_async_writev() - which re-repicks the server. If a different server is then selected, this causes the increment of server->in_flight to happen against one record and the decrement to happen against another, leading to misaccounting. Fix this by just removing the repick code in smb2_async_writev(). As this is only called from netfslib-driven code, cifs_prepare_write() should always have been called first, and so server should never be NULL and the preparatory step is repeated in the event that we do a retry. The problem manifests as a warning looking something like: WARNING: CPU: 4 PID: 72896 at fs/smb/client/smb2ops.c:97 smb2_add_credits+0x3f0/0x9e0 [cifs] ... RIP: 0010:smb2_add_credits+0x3f0/0x9e0 [cifs] ... smb2_writev_callback+0x334/0x560 [cifs] cifs_demultiplex_thread+0x77a/0x11b0 [cifs] kthread+0x187/0x1d0 ret_from_fork+0x34/0x60 ret_from_fork_asm+0x1a/0x30 Which may be triggered by a number of different xfstests running against an Azure server in multichannel mode. generic/249 seems the most repeatable, but generic/215, generic/249 and generic/308 may also show it.
CVE-2024-36031CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: keys: Fix overwrite of key expiration on instantiation The expiry time of a key is unconditionally overwritten during instantiation, defaulting to turn it permanent. This causes a problem for DNS resolution as the expiration set by user-space is overwritten to TIME64_MAX, disabling further DNS updates. Fix this by restoring the condition that key_set_expiry is only called when the pre-parser sets a specific expiry.
CVE-2024-38612CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: fix invalid unregister error path The error path of seg6_init() is wrong in case CONFIG_IPV6_SEG6_LWTUNNEL is not defined. In that case if seg6_hmac_init() fails, the genl_unregister_family() isn't called. This issue exist since commit 46738b1317e1 ("ipv6: sr: add option to control lwtunnel support"), and commit 5559cea2d5aa ("ipv6: sr: fix possible use-after-free and null-ptr-deref") replaced unregister_pernet_subsys() with genl_unregister_family() in this error path.
CVE-2024-38623CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Use variable length array instead of fixed size Should fix smatch warning: ntfs_set_label() error: __builtin_memcpy() 'uni->name' too small (20 vs 256)
CVE-2021-47548CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port() The if statement: if (port >= DSAF_GE_NUM) return; limits the value of port less than DSAF_GE_NUM (i.e., 8). However, if the value of port is 6 or 7, an array overflow could occur: port_rst_off = dsaf_dev->mac_cb[port]->port_rst_off; because the length of dsaf_dev->mac_cb is DSAF_MAX_PORT_NUM (i.e., 6). To fix this possible array overflow, we first check port and if it is greater than or equal to DSAF_MAX_PORT_NUM, the function returns.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-58034. Free for 1 server.

Get started free