{"api_version":"1","generated_at":"2026-10-01T07:41:47+00:00","cve":"CVE-2026-97979","urls":{"html":"https://cve.report/CVE-2026-97979","api":"https://cve.report/api/cve/CVE-2026-97979.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-97979","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-97979"},"summary":{"title":"ice: add missing xa_destroy for sched_node_ids","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nice: add missing xa_destroy for sched_node_ids\n\nCommit 16dfa49406bc (\"ice: Introduce new parameters in ice_sched_node\")\nadded a sched_node_ids xarray to the port info structure, but never called\nxa_destroy on it.\n\nSince xarrays can allocate internal memory, this can result in a memory\nleak even if every element in the xarray has been removed.\n\nThe xarray is currently embedded in the port_info structure. This appears\nto have been done because its use is within functions that take the\nport_info as a primary argument.\n\nHowever, this complicates managing the lifecycle of the field. The\nport_info structure is allocated in ice_init_hw() using devm, and it is\nnot released until the devm cleanup when the driver is unloaded.\n\nThe ice_init_hw() function is called in many places, including devlink\nreload, and possibly during DDP load after updating the Tx scheduler\nlayout.\n\nAdding a call of xa_destroy to the ice_deinit_hw() causes Sashiko to raise\nmultiple concerns due to potential ordering issues and possible ways that\nport_info could be a dangling reference.\n\nTo handle this, move the sched_node_ids out of port_info and into the hw\nstructure. All users of the array already have a pointer to hw anyways, and\nthere is only one sched_node_ids per adapter. While here, remove the overly\nverbose comment explaining the nature of the sched_node_ids xarray.\n\nAdd the missing xa_destroy to the cleanup path and to ice_deinit_hw(),\nensuring that we properly release the xarray memory.\n\nThis was caught by Sashiko during development of unrelated code.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-25 11:17:25","updated_at":"2026-09-25 11:17:25"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/d6f38fb12069fb1edf762962b5fcf3f42d643b47","name":"https://git.kernel.org/stable/c/d6f38fb12069fb1edf762962b5fcf3f42d643b47","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/f5463bc124c0d6f922e272336584730c5c61c4f1","name":"https://git.kernel.org/stable/c/f5463bc124c0d6f922e272336584730c5c61c4f1","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/53432c4c3e869076350aef319534431af8ba99c1","name":"https://git.kernel.org/stable/c/53432c4c3e869076350aef319534431af8ba99c1","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/44cdd6b7e036303f7fecf841cf23c05a4a4faf2d","name":"https://git.kernel.org/stable/c/44cdd6b7e036303f7fecf841cf23c05a4a4faf2d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-97979","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97979","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 16dfa49406bc5e1f4cbb115027cbd719d7e6c930 44cdd6b7e036303f7fecf841cf23c05a4a4faf2d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 16dfa49406bc5e1f4cbb115027cbd719d7e6c930 f5463bc124c0d6f922e272336584730c5c61c4f1 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 16dfa49406bc5e1f4cbb115027cbd719d7e6c930 d6f38fb12069fb1edf762962b5fcf3f42d643b47 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 16dfa49406bc5e1f4cbb115027cbd719d7e6c930 53432c4c3e869076350aef319534431af8ba99c1 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected a388961be5ed8ee037ac68220e389bc4e9339a39 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.1.95 6.2 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.2","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.2 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.111 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.53 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.7 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"97979","cve":"CVE-2026-97979","epss":"0.001680000","percentile":"0.053970000","score_date":"2026-09-27","updated_at":"2026-09-28 00:02:24"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/net/ethernet/intel/ice/ice_common.c","drivers/net/ethernet/intel/ice/ice_sched.c","drivers/net/ethernet/intel/ice/ice_type.h"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"44cdd6b7e036303f7fecf841cf23c05a4a4faf2d","status":"affected","version":"16dfa49406bc5e1f4cbb115027cbd719d7e6c930","versionType":"git"},{"lessThan":"f5463bc124c0d6f922e272336584730c5c61c4f1","status":"affected","version":"16dfa49406bc5e1f4cbb115027cbd719d7e6c930","versionType":"git"},{"lessThan":"d6f38fb12069fb1edf762962b5fcf3f42d643b47","status":"affected","version":"16dfa49406bc5e1f4cbb115027cbd719d7e6c930","versionType":"git"},{"lessThan":"53432c4c3e869076350aef319534431af8ba99c1","status":"affected","version":"16dfa49406bc5e1f4cbb115027cbd719d7e6c930","versionType":"git"},{"status":"affected","version":"a388961be5ed8ee037ac68220e389bc4e9339a39","versionType":"git"},{"lessThan":"6.2","status":"affected","version":"6.1.95","versionType":"semver"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/net/ethernet/intel/ice/ice_common.c","drivers/net/ethernet/intel/ice/ice_sched.c","drivers/net/ethernet/intel/ice/ice_type.h"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.2"},{"lessThan":"6.2","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.111","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.53","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.7","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.111","versionStartIncluding":"6.2","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.53","versionStartIncluding":"6.2","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.7","versionStartIncluding":"6.2","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc3","versionStartIncluding":"6.2","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.1.95","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nice: add missing xa_destroy for sched_node_ids\n\nCommit 16dfa49406bc (\"ice: Introduce new parameters in ice_sched_node\")\nadded a sched_node_ids xarray to the port info structure, but never called\nxa_destroy on it.\n\nSince xarrays can allocate internal memory, this can result in a memory\nleak even if every element in the xarray has been removed.\n\nThe xarray is currently embedded in the port_info structure. This appears\nto have been done because its use is within functions that take the\nport_info as a primary argument.\n\nHowever, this complicates managing the lifecycle of the field. The\nport_info structure is allocated in ice_init_hw() using devm, and it is\nnot released until the devm cleanup when the driver is unloaded.\n\nThe ice_init_hw() function is called in many places, including devlink\nreload, and possibly during DDP load after updating the Tx scheduler\nlayout.\n\nAdding a call of xa_destroy to the ice_deinit_hw() causes Sashiko to raise\nmultiple concerns due to potential ordering issues and possible ways that\nport_info could be a dangling reference.\n\nTo handle this, move the sched_node_ids out of port_info and into the hw\nstructure. All users of the array already have a pointer to hw anyways, and\nthere is only one sched_node_ids per adapter. While here, remove the overly\nverbose comment explaining the nature of the sched_node_ids xarray.\n\nAdd the missing xa_destroy to the cleanup path and to ice_deinit_hw(),\nensuring that we properly release the xarray memory.\n\nThis was caught by Sashiko during development of unrelated code."}],"providerMetadata":{"dateUpdated":"2026-09-25T10:23:16.422Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/44cdd6b7e036303f7fecf841cf23c05a4a4faf2d"},{"url":"https://git.kernel.org/stable/c/f5463bc124c0d6f922e272336584730c5c61c4f1"},{"url":"https://git.kernel.org/stable/c/d6f38fb12069fb1edf762962b5fcf3f42d643b47"},{"url":"https://git.kernel.org/stable/c/53432c4c3e869076350aef319534431af8ba99c1"}],"title":"ice: add missing xa_destroy for sched_node_ids","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-97979","datePublished":"2026-09-25T10:23:16.422Z","dateReserved":"2026-09-25T10:18:58.208Z","dateUpdated":"2026-09-25T10:23:16.422Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-25 11:17:25","lastModifiedDate":"2026-09-25 11:17:25","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"97979","Ordinal":"1","Title":"ice: add missing xa_destroy for sched_node_ids","CVE":"CVE-2026-97979","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"97979","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nice: add missing xa_destroy for sched_node_ids\n\nCommit 16dfa49406bc (\"ice: Introduce new parameters in ice_sched_node\")\nadded a sched_node_ids xarray to the port info structure, but never called\nxa_destroy on it.\n\nSince xarrays can allocate internal memory, this can result in a memory\nleak even if every element in the xarray has been removed.\n\nThe xarray is currently embedded in the port_info structure. This appears\nto have been done because its use is within functions that take the\nport_info as a primary argument.\n\nHowever, this complicates managing the lifecycle of the field. The\nport_info structure is allocated in ice_init_hw() using devm, and it is\nnot released until the devm cleanup when the driver is unloaded.\n\nThe ice_init_hw() function is called in many places, including devlink\nreload, and possibly during DDP load after updating the Tx scheduler\nlayout.\n\nAdding a call of xa_destroy to the ice_deinit_hw() causes Sashiko to raise\nmultiple concerns due to potential ordering issues and possible ways that\nport_info could be a dangling reference.\n\nTo handle this, move the sched_node_ids out of port_info and into the hw\nstructure. All users of the array already have a pointer to hw anyways, and\nthere is only one sched_node_ids per adapter. While here, remove the overly\nverbose comment explaining the nature of the sched_node_ids xarray.\n\nAdd the missing xa_destroy to the cleanup path and to ice_deinit_hw(),\nensuring that we properly release the xarray memory.\n\nThis was caught by Sashiko during development of unrelated code.","Type":"Description","Title":"ice: add missing xa_destroy for sched_node_ids"}]}}}