CVE-2026-46162: ice: fix double free in ice_sf_eth_activate() error path
In the Linux kernel, the following vulnerability has been resolved:
ice: fix double free in ice_sf_eth_activate() error path
When auxiliary_device_add() fails, ice_sf_eth_activate() jumps to
aux_dev_uninit and calls auxiliary_device_uninit(&sf_dev->adev).
The device release callback ice_sf_dev_release() frees sf_dev, but
the current error path falls through to sf_dev_free and calls
kfree(sf_dev) again, causing a double free.
Keep kfree(sf_dev) for the auxiliary_device_init() failure path, but
avoid falling through to sf_dev_free after auxiliary_device_uninit().
Security readout for executives and security teams
Plain-English summary
CVE-2026-46162 is a Linux kernel memory-management bug in the ice Ethernet driver. In a specific failure path, the kernel can free the same object twice. Public sources do not provide CVSS, exploitation evidence, or business-impact details. Treat this as a kernel stability and potential security issue requiring normal patch triage.
Executive priority
Schedule remediation through standard kernel patch cycles, with priority for servers using Intel ice-networked environments. Escalate if vendors assign high severity, release urgent advisories, or exploitation evidence appears.
Technical view
The bug is in ice_sf_eth_activate(). If auxiliary_device_add() fails, the path calls auxiliary_device_uninit(&sf_dev->adev). The release callback frees sf_dev, but execution then falls through to kfree(sf_dev), causing a double free. The fix avoids that fall-through while retaining kfree() for the auxiliary_device_init() failure path.
Likely exposure
Exposure appears limited to Linux kernels containing the vulnerable ice driver code path. The source lists Linux as affected, with version data including 6.12, 6.12.88, 6.18.30, 7.0.7, and 7.1. Validate against your distribution’s kernel package and backported fixes.
Exploitation context
No cited source reports active exploitation, and CISA KEV status is false in the provided data. The trigger is a specific error path when auxiliary_device_add() fails during ice subfunction Ethernet activation. Public sources do not define attacker prerequisites or remote exploitability.
Researcher notes
The public record describes the code defect and stable commit references but lacks CVSS, CWE, exploitability analysis, and distro-specific package status. Version information in the source appears broad and should be reconciled with vendor backports before declaring systems vulnerable.
Mitigation direction
Check Linux distribution or kernel vendor guidance for fixed packages.
Update to a kernel build containing the referenced stable fixes.
Prioritize systems using the Linux ice Ethernet driver.
If patching is delayed, monitor vendor advisories for supported workarounds.
Validation and detection
Inventory Linux kernel versions across affected assets.
Determine whether the ice driver is present or in use.
Verify whether vendor kernels include the referenced stable commits.
Track CVE status for CVSS, advisories, or exploitation updates.
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-2026-46162 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.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 28, 2026, 09:36 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.