CVE-2026-97979ice: add missing xa_destroy for sched_node_ids
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 3, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from a388961be5ed8ee037ac68220e389bc4e9339a39 before 09a7cdf8fffb065a8aa30cfa604ff4a65cbf04c9; from 16dfa49406bc5e1f4cbb115027cbd719d7e6c930 before c075a91fe5762d314e6e182d37d29cf874bd314a; from 16dfa49406bc5e1f4cbb115027cbd719d7e6c930 before 44cdd6b7e036303f7fecf841cf23c05a4a4faf2d; from 16dfa49406bc5e1f4cbb115027cbd719d7e6c930 before f5463bc124c0d6f922e272336584730c5c61c4f1; from 16dfa49406bc5e1f4cbb115027cbd719d7e6c930 before d6f38fb12069fb1edf762962b5fcf3f42d643b47; from 16dfa49406bc5e1f4cbb115027cbd719d7e6c930 before 53432c4c3e869076350aef319534431af8ba99c1; from 6.1.95 before 6.1.189 | CNA record |
References
- https://git.kernel.org/stable/c/09a7cdf8fffb065a8aa30cfa604ff4a65cbf04c9
- https://git.kernel.org/stable/c/c075a91fe5762d314e6e182d37d29cf874bd314a
- https://git.kernel.org/stable/c/44cdd6b7e036303f7fecf841cf23c05a4a4faf2d
- https://git.kernel.org/stable/c/f5463bc124c0d6f922e272336584730c5c61c4f1
- https://git.kernel.org/stable/c/d6f38fb12069fb1edf762962b5fcf3f42d643b47
- https://git.kernel.org/stable/c/53432c4c3e869076350aef319534431af8ba99c1
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.