CVE-2026-64161: net: ti: icssm-prueth: fix eth_ports_node leak in probe
Greg Kroah-Hartman <[email protected]>
| Newsgroups | org.kernel.vger.linux-cve-announce |
|---|---|
| Message-ID | <2026071934-CVE-2026-64161-0f95@gregkh> |
From: Greg Kroah-Hartman <[email protected]> Description =========== In the Linux kernel, the following vulnerability has been resolved: net: ti: icssm-prueth: fix eth_ports_node leak in probe The error path on of_property_read_u32() failure inside icssm_prueth_probe() returns without putting eth_ports_node, which was acquired before the for_each_child_of_node() loop. Drop it before returning. The Linux kernel CVE team has assigned CVE-2026-64161 to this issue. Affected and fixed versions =========================== Issue introduced in 6.18 with commit 511f6c1ae093c7045742299d29eba71925709a71 and fixed in 6.18.34 with commit 994358adc0982d17731ffea7dfacd25afcc89773 Issue introduced in 6.18 with commit 511f6c1ae093c7045742299d29eba71925709a71 and fixed in 7.0.11 with commit ca029dde6ad732a5aba28d6b107d7a84ba5e302b Issue introduced in 6.18 with commit 511f6c1ae093c7045742299d29eba71925709a71 and fixed in 7.1 with commit 6635fa84403c3a59455b66007c019a7cc632db30 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-2026-64161 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/net/ethernet/ti/icssm/icssm_prueth.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/994358adc0982d17731ffea7dfacd25afcc89773 https://git.kernel.org/stable/c/ca029dde6ad732a5aba28d6b107d7a84ba5e302b https://git.kernel.org/stable/c/6635fa84403c3a59455b66007c019a7cc632db30