CVE-2025-38526: ice: add NULL check in eswitch lag check
In the Linux kernel, the following vulnerability has been resolved:
ice: add NULL check in eswitch lag check
The function icelagisswitchdevrunning() is being called from outside of the LAG event handler code. This results in the lag->uppernetdev being NULL sometimes. To avoid a NULL-pointer dereference, there needs to be a check before it is dereferenced.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Update the Linux kernel/ice driver so the LAG event handler performs a NULL-pointer check before dereferencing lag->upper_netdev (related to ice_lag_is_switchdev_running() being called from outside and sometimes causing NULL dereference).
Linux kernel (ice driver) NULL check in eswitch lag check (ice_lag_is_switchdev_running() / lag->upper_netdev dereference) = Add NULL check before dereferencing lag->upper_netdev in the LAG event handler code
Event History
Frequently Asked Questions
What is the severity of CVE-2025-38526?
CVE-2025-38526 is classified as a high severity vulnerability in the Linux kernel.
How do I fix CVE-2025-38526?
To fix CVE-2025-38526, you should update to the latest version of the Linux kernel that contains the patch addressing this vulnerability.
What systems are affected by CVE-2025-38526?
CVE-2025-38526 affects various versions of the Linux kernel where the specific ice driver functionality is utilized.
What is the nature of the issue in CVE-2025-38526?
CVE-2025-38526 involves a potential NULL pointer dereference in the ice driver when checking LAG status.
Has CVE-2025-38526 been resolved?
Yes, CVE-2025-38526 has been resolved in the Linux kernel with a patch that includes a NULL check in the relevant function.