PT-2026-98643 · Linux · Linux

CVE-2026-97979

·

Published

2026-09-25

·

Updated

2026-09-25

None

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
ice: add missing xa destroy for sched node ids
Commit 16dfa49406bc ("ice: Introduce new parameters in ice sched node") added a sched node ids xarray to the port info structure, but never called xa destroy on it.
Since xarrays can allocate internal memory, this can result in a memory leak even if every element in the xarray has been removed.
The xarray is currently embedded in the port info structure. This appears to have been done because its use is within functions that take the port info as a primary argument.
However, this complicates managing the lifecycle of the field. The port info structure is allocated in ice init hw() using devm, and it is not released until the devm cleanup when the driver is unloaded.
The ice init hw() function is called in many places, including devlink reload, and possibly during DDP load after updating the Tx scheduler layout.
Adding a call of xa destroy to the ice deinit hw() causes Sashiko to raise multiple concerns due to potential ordering issues and possible ways that port info could be a dangling reference.
To handle this, move the sched node ids out of port info and into the hw structure. All users of the array already have a pointer to hw anyways, and there is only one sched node ids per adapter. While here, remove the overly verbose comment explaining the nature of the sched node ids xarray.
Add the missing xa destroy to the cleanup path and to ice deinit hw(), ensuring that we properly release the xarray memory.
This was caught by Sashiko during development of unrelated code.
Found an issue in the description? Have something to add? Feel free to write us 👾

Related Identifiers

CVE-2026-97979

Affected Products

Linux