CVE-2026-97979

CVE CVE-2026-97979EUVD EUVD-2026-86633Veröffentlicht 2026-09-25T10:23:16.000Z

Was das Advisory beschreibt

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.

Quelle: EUVD (ENISA), im Wortlaut der Meldung.

Produkte, die das Advisory nennt

Diese Angaben stammen aus der Meldung selbst, nicht aus einer Prüfung durch uns.

• Linux — Linux 6.1.95 <6.2; 16dfa49406bc5e1f4cbb115027cbd719d7e6c930 <44cdd6b7e036303f7fecf841cf23c05a4a4faf2d; patch: 0; a388961be5ed8ee037ac68220e389bc4e9339a39; 16dfa49406bc5e1f4cbb115027cbd719d7e6c930 <f5463bc124c0d6f922e272336584730c5c61c4f1; patch: 6.18.53; patch: 6.12.111; patch: 7.2.7; 16dfa49406bc5e1f4cbb115027cbd719d7e6c930 <53432c4c3e869076350aef319534431af8ba99c1; patch: 7.3-rc3; 16dfa49406bc5e1f4cbb115027cbd719d7e6c930 <d6f38fb12069fb1edf762962b5fcf3f42d643b47; 6.2

Die genannten Versionen sind die Angabe der Meldung. Patchlage vergleicht keine Versionsnummern und leitet aus ihnen keine Aussage ab — welche Version installiert ist, muss ein Mensch nachsehen.

Im Produktkatalog geführt

Für diese Produkte kann ein Bestand in Patchlage erfasst werden. Ein Advisory dazu erscheint am Morgen danach im Lagebericht.

• Linux — Linux

Patchlage meldet Treffer und Verdachtsfälle. Zu allem anderen sagt dieses System nichts — weder diese Seite noch der Lagebericht behauptet je, dass ein Bestand sicher ist.