CVE-2024-38584: net: ti: icssg_prueth: Fix NULL pointer dereference in prueth_probe()
In the Linux kernel, the following vulnerability has been resolved:
net: ti: icssg_prueth: Fix NULL pointer dereference in prueth_probe()
In the prueth_probe() function, if one of the calls to emac_phy_connect()
fails due to of_phy_connect() returning NULL, then the subsequent call to
phy_attached_info() will dereference a NULL pointer.
Check the return code of emac_phy_connect and fail cleanly if there is an
error.
Security readout for executives and security teams
Plain-English summary
CVE-2024-38584 is a Linux kernel driver bug in TI ICSSG PRU Ethernet initialization. If PHY connection setup fails, the driver can dereference a null pointer during probe. The documented impact is reliability or availability risk, not data theft. The sources provide no CVSS score or confirmed exploitation.
Executive priority
Treat this as a targeted kernel reliability issue. It should be handled in normal kernel maintenance unless the organization depends on affected TI Ethernet hardware in production or safety-sensitive environments.
Technical view
The issue is in net/ti/icssg_prueth. prueth_probe() called phy_attached_info() after emac_phy_connect() without correctly handling a NULL result from of_phy_connect(). Kernel stable fixes add error handling so probe fails cleanly instead of dereferencing NULL.
Likely exposure
Exposure is most likely on Linux systems using the TI ICSSG PRU Ethernet driver, especially embedded or industrial platforms with affected kernel versions listed around 6.6 through 6.10. General Linux servers without this hardware or driver path are less likely exposed.
Exploitation context
The provided sources do not identify active exploitation, public exploit activity, or KEV listing. The condition appears tied to device initialization and PHY connection failure during driver probe, so practical impact depends on hardware, kernel build, and device configuration.
Researcher notes
Evidence is limited to the CVE record and Linux stable commit references. No CVSS, CWE, exploit report, or vendor-specific impact matrix is provided. Analysis should stay scoped to the NULL dereference in prueth_probe().
Mitigation direction
Update to a kernel build containing the relevant stable fix commits.
Check Linux distribution or device vendor advisories for backported fixes.
Prioritize affected embedded systems using TI ICSSG PRU Ethernet.
Avoid ad hoc driver disablement unless vendor guidance supports it.
Validation and detection
Inventory systems for affected Linux kernel versions and TI ICSSG PRU Ethernet usage.
Confirm vendor kernel changelogs include one of the cited stable commits.
Review boot or kernel logs for prueth_probe or PHY connection failures.
Track remediation status separately for vendor kernels with backports.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-38584 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.