{"api_version":"1","generated_at":"2026-10-04T10:53:26+00:00","cve":"CVE-2026-97603","urls":{"html":"https://cve.report/CVE-2026-97603","api":"https://cve.report/api/cve/CVE-2026-97603.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-97603","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-97603"},"summary":{"title":"idpf: disable DIM work before freeing q_vectors","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nidpf: disable DIM work before freeing q_vectors\n\nidpf never drains the Tx/Rx DIM works before freeing the memory they\nlive in.  tx_dim and rx_dim are embedded in struct idpf_q_vector, they\nare queued from the NAPI poll via net_dim(), and idpf_vport_intr_rel()\nends with kfree(rsrc->q_vectors).  Nothing in the driver cancels them.\n\nidpf_tx_dim_work() and idpf_rx_dim_work() then run on freed memory:\nidpf_vport_intr_write_itr() writes the ITR register through\nq_vector->intr_reg.tx_itr / rx_itr, void __iomem pointers loaded out of\nthe freed q_vector.  No configuration is needed to get there --\nIDPF_ITR_IS_DYNAMIC() is defined as (itr_mode) and idpf_vport_alloc()\ninitialises both modes to IDPF_ITR_DYNAMIC.\n\nDraining after idpf_vport_intr_napi_dis_all() is not enough on its own.\nidpf_net_dim() is called from inside the\n\"if (napi_complete_done(napi, work_done))\" branch of the poll, and\nnapi_complete_done() has already cleared NAPIF_STATE_SCHED by then.\nnapi_disable_locked() waits only while (val & (NAPIF_STATE_SCHED |\nNAPIF_STATE_NPSVC)), so napi_disable() can return while the poll tail is\nstill queueing the work, and a plain cancel_work_sync() would be\nre-armed behind the drain.\n\nUse disable_work_sync(): schedule_work() on a work with a non-zero\ndisable count is dropped by clear_pending_if_disabled() before\n__queue_work() is reached.\n\nMove idpf_init_dim() to idpf_vport_intr_alloc() so the works are\ninitialised on every path that can reach the drain -- the three\n\"goto intr_deinit\" sites between idpf_vport_intr_init() and\nidpf_vport_intr_ena() get there without the enable side having run.\nNothing re-enables them: rsrc->q_vectors is freed on every exit from\nidpf_vport_open() and on every idpf_vport_stop(), so the count dies with\nthe object.\n\nIt is a race, not a deterministic failure -- net_dim() only schedules\nonce DIM_NEVENTS events have accumulated and the profile index changes.\nA KASAN ifup/ifdown loop under load is the way to see it.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-25 11:17:13","updated_at":"2026-10-03 11:18:06"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/7e4312953788244d47074987d40d76702cf929f1","name":"https://git.kernel.org/stable/c/7e4312953788244d47074987d40d76702cf929f1","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/7d64d4c6bb6bb63b6cdb7de133c3ec48333b27b5","name":"https://git.kernel.org/stable/c/7d64d4c6bb6bb63b6cdb7de133c3ec48333b27b5","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/7dd4c829bac2916be98a3e34b41daaba7f42b4c4","name":"https://git.kernel.org/stable/c/7dd4c829bac2916be98a3e34b41daaba7f42b4c4","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/cd7a1598645b6917a8676b7e2efe8d97ce68a952","name":"https://git.kernel.org/stable/c/cd7a1598645b6917a8676b7e2efe8d97ce68a952","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-97603","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97603","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected c2d548cad1508d334517bcbd7cd5c915cc831fc0 7d64d4c6bb6bb63b6cdb7de133c3ec48333b27b5 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected c2d548cad1508d334517bcbd7cd5c915cc831fc0 7e4312953788244d47074987d40d76702cf929f1 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected c2d548cad1508d334517bcbd7cd5c915cc831fc0 cd7a1598645b6917a8676b7e2efe8d97ce68a952 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected c2d548cad1508d334517bcbd7cd5c915cc831fc0 7dd4c829bac2916be98a3e34b41daaba7f42b4c4 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.7","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.7 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.112 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":"97603","cve":"CVE-2026-97603","epss":"0.001980000","percentile":"0.086690000","score_date":"2026-10-03","updated_at":"2026-10-04 00:03:16"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/net/ethernet/intel/idpf/idpf_txrx.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"7d64d4c6bb6bb63b6cdb7de133c3ec48333b27b5","status":"affected","version":"c2d548cad1508d334517bcbd7cd5c915cc831fc0","versionType":"git"},{"lessThan":"7e4312953788244d47074987d40d76702cf929f1","status":"affected","version":"c2d548cad1508d334517bcbd7cd5c915cc831fc0","versionType":"git"},{"lessThan":"cd7a1598645b6917a8676b7e2efe8d97ce68a952","status":"affected","version":"c2d548cad1508d334517bcbd7cd5c915cc831fc0","versionType":"git"},{"lessThan":"7dd4c829bac2916be98a3e34b41daaba7f42b4c4","status":"affected","version":"c2d548cad1508d334517bcbd7cd5c915cc831fc0","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/net/ethernet/intel/idpf/idpf_txrx.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.7"},{"lessThan":"6.7","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.112","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.112","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.53","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.7","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc3","versionStartIncluding":"6.7","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nidpf: disable DIM work before freeing q_vectors\n\nidpf never drains the Tx/Rx DIM works before freeing the memory they\nlive in.  tx_dim and rx_dim are embedded in struct idpf_q_vector, they\nare queued from the NAPI poll via net_dim(), and idpf_vport_intr_rel()\nends with kfree(rsrc->q_vectors).  Nothing in the driver cancels them.\n\nidpf_tx_dim_work() and idpf_rx_dim_work() then run on freed memory:\nidpf_vport_intr_write_itr() writes the ITR register through\nq_vector->intr_reg.tx_itr / rx_itr, void __iomem pointers loaded out of\nthe freed q_vector.  No configuration is needed to get there --\nIDPF_ITR_IS_DYNAMIC() is defined as (itr_mode) and idpf_vport_alloc()\ninitialises both modes to IDPF_ITR_DYNAMIC.\n\nDraining after idpf_vport_intr_napi_dis_all() is not enough on its own.\nidpf_net_dim() is called from inside the\n\"if (napi_complete_done(napi, work_done))\" branch of the poll, and\nnapi_complete_done() has already cleared NAPIF_STATE_SCHED by then.\nnapi_disable_locked() waits only while (val & (NAPIF_STATE_SCHED |\nNAPIF_STATE_NPSVC)), so napi_disable() can return while the poll tail is\nstill queueing the work, and a plain cancel_work_sync() would be\nre-armed behind the drain.\n\nUse disable_work_sync(): schedule_work() on a work with a non-zero\ndisable count is dropped by clear_pending_if_disabled() before\n__queue_work() is reached.\n\nMove idpf_init_dim() to idpf_vport_intr_alloc() so the works are\ninitialised on every path that can reach the drain -- the three\n\"goto intr_deinit\" sites between idpf_vport_intr_init() and\nidpf_vport_intr_ena() get there without the enable side having run.\nNothing re-enables them: rsrc->q_vectors is freed on every exit from\nidpf_vport_open() and on every idpf_vport_stop(), so the count dies with\nthe object.\n\nIt is a race, not a deterministic failure -- net_dim() only schedules\nonce DIM_NEVENTS events have accumulated and the profile index changes.\nA KASAN ifup/ifdown loop under load is the way to see it."}],"providerMetadata":{"dateUpdated":"2026-10-03T11:00:07.561Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/7d64d4c6bb6bb63b6cdb7de133c3ec48333b27b5"},{"url":"https://git.kernel.org/stable/c/7e4312953788244d47074987d40d76702cf929f1"},{"url":"https://git.kernel.org/stable/c/cd7a1598645b6917a8676b7e2efe8d97ce68a952"},{"url":"https://git.kernel.org/stable/c/7dd4c829bac2916be98a3e34b41daaba7f42b4c4"}],"title":"idpf: disable DIM work before freeing q_vectors","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-97603","datePublished":"2026-09-25T10:22:16.015Z","dateReserved":"2026-09-24T16:01:01.158Z","dateUpdated":"2026-10-03T11:00:07.561Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-25 11:17:13","lastModifiedDate":"2026-10-03 11:18:06","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"97603","Ordinal":"1","Title":"idpf: disable DIM work before freeing q_vectors","CVE":"CVE-2026-97603","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"97603","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nidpf: disable DIM work before freeing q_vectors\n\nidpf never drains the Tx/Rx DIM works before freeing the memory they\nlive in.  tx_dim and rx_dim are embedded in struct idpf_q_vector, they\nare queued from the NAPI poll via net_dim(), and idpf_vport_intr_rel()\nends with kfree(rsrc->q_vectors).  Nothing in the driver cancels them.\n\nidpf_tx_dim_work() and idpf_rx_dim_work() then run on freed memory:\nidpf_vport_intr_write_itr() writes the ITR register through\nq_vector->intr_reg.tx_itr / rx_itr, void __iomem pointers loaded out of\nthe freed q_vector.  No configuration is needed to get there --\nIDPF_ITR_IS_DYNAMIC() is defined as (itr_mode) and idpf_vport_alloc()\ninitialises both modes to IDPF_ITR_DYNAMIC.\n\nDraining after idpf_vport_intr_napi_dis_all() is not enough on its own.\nidpf_net_dim() is called from inside the\n\"if (napi_complete_done(napi, work_done))\" branch of the poll, and\nnapi_complete_done() has already cleared NAPIF_STATE_SCHED by then.\nnapi_disable_locked() waits only while (val & (NAPIF_STATE_SCHED |\nNAPIF_STATE_NPSVC)), so napi_disable() can return while the poll tail is\nstill queueing the work, and a plain cancel_work_sync() would be\nre-armed behind the drain.\n\nUse disable_work_sync(): schedule_work() on a work with a non-zero\ndisable count is dropped by clear_pending_if_disabled() before\n__queue_work() is reached.\n\nMove idpf_init_dim() to idpf_vport_intr_alloc() so the works are\ninitialised on every path that can reach the drain -- the three\n\"goto intr_deinit\" sites between idpf_vport_intr_init() and\nidpf_vport_intr_ena() get there without the enable side having run.\nNothing re-enables them: rsrc->q_vectors is freed on every exit from\nidpf_vport_open() and on every idpf_vport_stop(), so the count dies with\nthe object.\n\nIt is a race, not a deterministic failure -- net_dim() only schedules\nonce DIM_NEVENTS events have accumulated and the profile index changes.\nA KASAN ifup/ifdown loop under load is the way to see it.","Type":"Description","Title":"idpf: disable DIM work before freeing q_vectors"}]}}}