CVE-2024-35945: net: phy: phy_device: Prevent nullptr exceptions on ISR
In the Linux kernel, the following vulnerability has been resolved:
net: phy: phy_device: Prevent nullptr exceptions on ISR
If phydev->irq is set unconditionally, check
for valid interrupt handler or fall back to polling mode to prevent
nullptr exceptions in interrupt service routine.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel networking bug in PHY interrupt handling. In affected kernels, a device interrupt can reach missing handler logic and trigger a null pointer exception, likely causing instability or a crash. The sources do not provide CVSS scoring, exploit details, or broad impact evidence.
Executive priority
Track for normal-to-expedited kernel maintenance, with higher priority for network appliances and systems where kernel crashes affect availability. Current public evidence does not support emergency response on its own.
Technical view
The resolved kernel change checks whether a valid PHY interrupt handler exists when phydev->irq is set. If not, it falls back to polling mode to avoid null pointer exceptions inside the interrupt service routine. Exposure depends on affected kernel versions and relevant PHY/network driver behavior.
Likely exposure
Organizations running affected Linux kernel versions or downstream vendor kernels may be exposed, especially on systems using PHY network hardware with interrupt-driven link handling. The provided affected-version data is limited and should be verified against vendor kernel advisories.
Exploitation context
The bundle does not cite active exploitation, public exploit availability, or KEV listing. Treat this as a reliability and possible availability issue unless vendor guidance provides stronger impact evidence.
Researcher notes
Key review point is whether phydev->irq can be configured without a valid handler in affected code paths. The fix direction is defensive validation and polling fallback, not a documented remote exploit path.
Mitigation direction
Apply vendor kernel updates that include the referenced stable fixes.
If self-maintaining kernels, review and merge the relevant stable commits.
Prioritize internet-facing, network-critical, embedded, and appliance Linux systems.
Check vendor advisories for distro-specific fixed package versions.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and embedded devices.
Compare kernel builds with CVE-2024-35945 and the referenced stable commits.
Confirm downstream vendor kernels include the PHY interrupt handling fix.
Review crash logs for PHY interrupt or null pointer exception patterns.
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-35945 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.