CVE-2026-97979
- Source
- https://cve.org/CVERecord?id=CVE-2026-97979
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-97979.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-97979
- Downstream
- Related
- Published
- 2026-09-25T10:23:16Z
- Modified
- 2026-10-09T17:27:04Z
- Summary
- ice: add missing xa_destroy for sched_node_ids
- Details
-
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.
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/97xxx/CVE-2026-97979.json" }- References
-
- https://git.kernel.org/stable/c/09a7cdf8fffb065a8aa30cfa604ff4a65cbf04c9
- https://git.kernel.org/stable/c/44cdd6b7e036303f7fecf841cf23c05a4a4faf2d
- https://git.kernel.org/stable/c/53432c4c3e869076350aef319534431af8ba99c1
- https://git.kernel.org/stable/c/c075a91fe5762d314e6e182d37d29cf874bd314a
- https://git.kernel.org/stable/c/d6f38fb12069fb1edf762962b5fcf3f42d643b47
- https://git.kernel.org/stable/c/f5463bc124c0d6f922e272336584730c5c61c4f1
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/97xxx/CVE-2026-97979.json
- https://nvd.nist.gov/vuln/detail/CVE-2026-97979
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduceda388961be5ed8ee037ac68220e389bc4e9339a39Fixed09a7cdf8fffb065a8aa30cfa604ff4a65cbf04c9
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced16dfa49406bc5e1f4cbb115027cbd719d7e6c930Fixedc075a91fe5762d314e6e182d37d29cf874bd314aFixed44cdd6b7e036303f7fecf841cf23c05a4a4faf2dFixedf5463bc124c0d6f922e272336584730c5c61c4f1Fixedd6f38fb12069fb1edf762962b5fcf3f42d643b47Fixed53432c4c3e869076350aef319534431af8ba99c1
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced6.1.95Fixed6.1.189
Affected versions
v6.*
Linux / Kernel
Package
- Name
- Kernel
Affected ranges
- Type
- ECOSYSTEM
- Events
-
Introduced0 Unknown introduced version / All previous versions are affectedFixed6.1.189
- Type
- ECOSYSTEM
- Events
-
Introduced6.2.0Fixed6.6.158Fixed6.12.111
- Type
- ECOSYSTEM
- Events
-
Introduced6.7.0Fixed6.18.53
- Type
- ECOSYSTEM
- Events
-
Introduced6.13.0Fixed7.2.7