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 ice_lag_is_switchdev_running() is being called from outside of
the LAG event handler code. This results in the lag->upper_netdev being
NULL sometimes. To avoid a NULL-pointer dereference, there needs to be a
check before it is dereferenced.
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux kernel’s Intel Ethernet “ice” driver can dereference a missing network-device pointer during switchdev/LAG checks, potentially crashing the system. The documented impact is loss of availability, not data theft or modification.
Executive priority
Treat as high priority for network infrastructure and availability-sensitive hosts using the affected driver features. Accelerate patch validation there; use normal risk-based scheduling elsewhere after confirming exposure. No evidence supplied supports declaring an active exploitation emergency.
Technical view
ice_lag_is_switchdev_running() may execute outside the LAG event handler while lag->upper_netdev is NULL. Dereferencing it can cause a kernel NULL-pointer fault. The supplied CVSS 3.1 score is 7.5, with network reachability, low complexity, no privileges, no user interaction, and availability-only impact.
Likely exposure
Exposure is most likely on Linux systems using the Intel ice network driver with eswitch switchdev or link-aggregation behavior. The supplied version data names Linux 6.6, 6.6.100, 6.12.40, 6.15.8, and 6.16, but its exact range semantics are unclear. Confirm downstream distribution status.
Exploitation context
The bundle does not identify CISA KEV listing, active exploitation, public proof-of-concept code, or a demonstrated remote attack path. Although the supplied CVSS vector says network-accessible and unauthenticated, the sources provided do not explain how an attacker could reliably reach the faulty state.
Researcher notes
The core defect and fix direction are clear, but affected-version presentation is ambiguous: the bundle includes repeated commit identifiers and standalone release numbers without explicit range operators. Researchers should inspect the referenced stable commits and downstream backports before declaring a build vulnerable. Trigger controllability and practical remote exploitability remain unproven here.
Mitigation direction
Apply a vendor-supported kernel containing the referenced NULL-check fix.
Check distribution advisories for corrected package versions and required reboot guidance.
Prioritize systems using the ice driver with switchdev or link aggregation.
If immediate updating is impossible, consult vendor guidance for supported feature-level mitigations.
Validation and detection
Inventory running kernels and identify systems loading the ice driver.
Determine whether affected systems use eswitch switchdev or link aggregation.
Map installed kernel packages against distribution-specific advisories and fixed versions.
After updating, reboot and confirm the corrected kernel is running.
Review kernel logs for NULL dereferences or crashes involving ice LAG functions.
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-2025-38526 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.
1CVSS vectors
3Timeline events
0ADP providers
5Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.