cveboard RSS feed

CVE-2026-97979

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2026
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

ice: add missing xa_destroy for sched_node_ids

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.

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
a388961be5ed8ee037ac68220e389bc4e9339a39affectedgit09a7cdf8fffb065a8aa30cfa604ff4a65cbf04c9UnavailableNone listed
16dfa49406bc5e1f4cbb115027cbd719d7e6c930affectedgitc075a91fe5762d314e6e182d37d29cf874bd314aUnavailableNone listed
16dfa49406bc5e1f4cbb115027cbd719d7e6c930affectedgit44cdd6b7e036303f7fecf841cf23c05a4a4faf2dUnavailableNone listed
16dfa49406bc5e1f4cbb115027cbd719d7e6c930affectedgitf5463bc124c0d6f922e272336584730c5c61c4f1UnavailableNone listed
16dfa49406bc5e1f4cbb115027cbd719d7e6c930affectedgitd6f38fb12069fb1edf762962b5fcf3f42d643b47UnavailableNone listed
16dfa49406bc5e1f4cbb115027cbd719d7e6c930affectedgit53432c4c3e869076350aef319534431af8ba99c1UnavailableNone listed
6.1.95affectedsemver6.1.189UnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
6.2affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver6.2UnavailableNone listed
6.1.189unaffectedsemverUnavailable6.1.*None listed
6.6.158unaffectedsemverUnavailable6.6.*None listed
6.12.111unaffectedsemverUnavailable6.12.*None listed
6.18.53unaffectedsemverUnavailable6.18.*None listed
7.2.7unaffectedsemverUnavailable7.2.*None listed
7.3unaffectedoriginal_commit_for_fixUnavailable*None listed