ice: add missing xa_destroy for sched_node_ids
Summary
| CVE | CVE-2026-97979 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-25 11:17:25 UTC |
| Updated | 2026-09-25 11:17:25 UTC |
| Description | 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. |
Risk And Classification
EPSS: 0.001680000 probability, percentile 0.053970000 (date 2026-09-27)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 16dfa49406bc5e1f4cbb115027cbd719d7e6c930 44cdd6b7e036303f7fecf841cf23c05a4a4faf2d git | Not specified |
| CNA | Linux | Linux | affected 16dfa49406bc5e1f4cbb115027cbd719d7e6c930 f5463bc124c0d6f922e272336584730c5c61c4f1 git | Not specified |
| CNA | Linux | Linux | affected 16dfa49406bc5e1f4cbb115027cbd719d7e6c930 d6f38fb12069fb1edf762962b5fcf3f42d643b47 git | Not specified |
| CNA | Linux | Linux | affected 16dfa49406bc5e1f4cbb115027cbd719d7e6c930 53432c4c3e869076350aef319534431af8ba99c1 git | Not specified |
| CNA | Linux | Linux | affected a388961be5ed8ee037ac68220e389bc4e9339a39 git | Not specified |
| CNA | Linux | Linux | affected 6.1.95 6.2 semver | Not specified |
| CNA | Linux | Linux | affected 6.2 | Not specified |
| CNA | Linux | Linux | unaffected 6.2 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.111 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.53 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.7 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3-rc3 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/d6f38fb12069fb1edf762962b5fcf3f42d643b47 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/f5463bc124c0d6f922e272336584730c5c61c4f1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/53432c4c3e869076350aef319534431af8ba99c1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/44cdd6b7e036303f7fecf841cf23c05a4a4faf2d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.