CVE-2026-97979: ice: add missing xa_destroy for sched_node_ids
ice: add missing xadestroy for schednodeids
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.158.1-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.190-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.113-1~deb12u1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1 - Compensating control
In the ice driver, move the sched_node_ids xarray from port_info into the hw structure and call xa_destroy for it in both the cleanup path and ice_deinit_hw() so its internal memory is released.
Event History
Frequently Asked Questions
Which systems are most likely to accumulate the leaked memory?
Systems using the Linux kernel ice driver are most exposed when ice_init_hw() is invoked repeatedly. The description specifically identifies devlink reload as one such path, and notes that DDP loading after a Tx scheduler layout update may also invoke it.
What can be done if the fix cannot be applied immediately?
Minimize repeated devlink reload operations on affected systems, since they can reinitialize the hardware while the port_info allocation remains until the driver is unloaded. Also review workflows that load DDP packages after Tx scheduler layout changes, as this may be another initialization path.