Answer in brief
CVE-2024-58034 records a Unknown severity vulnerability in memory: tegra20-emc: fix an OF node reference bug in tegra_emc_find_node_by_ram_code(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2024-58034 records a Unknown severity vulnerability in memory: tegra20-emc: fix an OF node reference bug in tegra_emc_find_node_by_ram_code(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=96e5da7c842424bcf64afe1082b960b42b96190b <c3def10c610ae046aaa61d00528e7bd15e4ad8d3 || >=96e5da7c842424bcf64afe1082b960b42b96190b <e9d07e91de140679eeaf275f47ad154467cb9e05 || >=96e5da7c842424bcf64afe1082b960b42b96190b <c144423cb07e4e227a8572d5742ca2b36ada770d || >=96e5da7c842424bcf64afe1082b960b42b96190b <3b02273446e23961d910b50cc12528faec649fb2 || >=96e5da7c842424bcf64afe1082b960b42b96190b <755e44538c190c31de9090d8e8821d228fcfd416 || >=96e5da7c842424bcf64afe1082b960b42b96190b <b9784e5cde1f9fb83661a70e580e381ae1264d12 | c3def10c610ae046aaa61d00528e7bd15e4ad8d3, e9d07e91de140679eeaf275f47ad154467cb9e05, c144423cb07e4e227a8572d5742ca2b36ada770d, 3b02273446e23961d910b50cc12528faec649fb2, 755e44538c190c31de9090d8e8821d228fcfd416, b9784e5cde1f9fb83661a70e580e381ae1264d12 |
| Linux/Linuxgeneric | 5.0 | Not reported |
Published upstream
Feb 27, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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]
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=96e5da7c842424bcf64afe1082b960b42b96190b <c3def10c610ae046aaa61d00528e7bd15e4ad8d3 || >=96e5da7c842424bcf64afe1082b960b42b96190b <e9d07e91de140679eeaf275f47ad154467cb9e05 || >=96e5da7c842424bcf64afe1082b960b42b96190b <c144423cb07e4e227a8572d5742ca2b36ada770d || >=96e5da7c842424bcf64afe1082b960b42b96190b <3b02273446e23961d910b50cc12528faec649fb2 || >=96e5da7c842424bcf64afe1082b960b42b96190b <755e44538c190c31de9090d8e8821d228fcfd416 || >=96e5da7c842424bcf64afe1082b960b42b96190b <b9784e5cde1f9fb83661a70e580e381ae1264d12 | c3def10c610ae046aaa61d00528e7bd15e4ad8d3, e9d07e91de140679eeaf275f47ad154467cb9e05, c144423cb07e4e227a8572d5742ca2b36ada770d, 3b02273446e23961d910b50cc12528faec649fb2, 755e44538c190c31de9090d8e8821d228fcfd416, b9784e5cde1f9fb83661a70e580e381ae1264d12 |
| Linux/Linuxgeneric | 5.0 | Not reported |
Published upstream
Feb 27, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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]
Quoted source text, attributed separately from HOL analysis.