{"api_version":"1","generated_at":"2026-10-27T16:46:40+00:00","cve":"CVE-2026-98617","urls":{"html":"https://cve.report/CVE-2026-98617","api":"https://cve.report/api/cve/CVE-2026-98617.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-98617","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-98617"},"summary":{"title":"eth: fbnic: use the Rx queue napi pointer to find the napi vector","description":"In the Linux kernel, the following vulnerability has been resolved:\n\neth: fbnic: use the Rx queue napi pointer to find the napi vector\n\nThe queue management ndos pick the napi vector for an Rx queue with:\n\tnv = fbn->napi[idx % fbn->num_napi];\n\nThe issue is this is only correct in the cases where there are no\nstandalone Tx vectors. In those cases we were allocating the Tx vectors\nfirst and then the Rx so the queues would be pointing to Tx NAPI vectors\ninstead of the Rx ones.\n\nThe mapping the ndos want is already recorded.  fbnic_set_netif_napi()\npublishes it with netif_queue_set_napi(), which stores the napi pointer\nin netdev_rx_queue.napi, and fbnic_reset_netif_napi() clears it again.\nBoth run under the netdev instance lock that the queue management ndos\nalso hold, so the pointer can be read directly.\n\nUse it and drop the divide.  The pointer is NULL exactly while the\ndatapath is down, so fbnic_queue_mem_alloc() can reject that case rather\nthan reaching into freed state: netdev_rx_queue_restart() calls it\nbefore it tests netif_running(), and fbnic_pm_suspend() leaves\nnetif_running() true across a PCIe recovery that never completes, so a\nqueue restart can arrive after fbnic_stop() has freed the rings and the\nvectors.  fbnic_stop() clears the association in\nfbnic_reset_netif_queues() before fbnic_free_napi_vectors(), so the\nNULL is always published first.  fbnic_queue_start() and\nfbnic_queue_stop() need no check of their own, as\nnetdev_rx_queue_reconfig() only reaches them once fbnic_queue_mem_alloc()\nhas succeeded under the same instance lock.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-10-18 16:17:14","updated_at":"2026-10-19 10:19:25"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/b5d9e9d4d0c13bc8b60d8d97e7a07fb25fea639e","name":"https://git.kernel.org/stable/c/b5d9e9d4d0c13bc8b60d8d97e7a07fb25fea639e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/1fb569cf3bf97e552f465b2c719e36b48ae7c18b","name":"https://git.kernel.org/stable/c/1fb569cf3bf97e552f465b2c719e36b48ae7c18b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-98617","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98617","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected da43127a8edc7498cce7b2554533f4027c618933 1fb569cf3bf97e552f465b2c719e36b48ae7c18b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected da43127a8edc7498cce7b2554533f4027c618933 b5d9e9d4d0c13bc8b60d8d97e7a07fb25fea639e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.18","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.9 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/net/ethernet/meta/fbnic/fbnic_txrx.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"1fb569cf3bf97e552f465b2c719e36b48ae7c18b","status":"affected","version":"da43127a8edc7498cce7b2554533f4027c618933","versionType":"git"},{"lessThan":"b5d9e9d4d0c13bc8b60d8d97e7a07fb25fea639e","status":"affected","version":"da43127a8edc7498cce7b2554533f4027c618933","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/net/ethernet/meta/fbnic/fbnic_txrx.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.18"},{"lessThan":"6.18","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.9","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.9","versionStartIncluding":"6.18","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3","versionStartIncluding":"6.18","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\neth: fbnic: use the Rx queue napi pointer to find the napi vector\n\nThe queue management ndos pick the napi vector for an Rx queue with:\n\tnv = fbn->napi[idx % fbn->num_napi];\n\nThe issue is this is only correct in the cases where there are no\nstandalone Tx vectors. In those cases we were allocating the Tx vectors\nfirst and then the Rx so the queues would be pointing to Tx NAPI vectors\ninstead of the Rx ones.\n\nThe mapping the ndos want is already recorded.  fbnic_set_netif_napi()\npublishes it with netif_queue_set_napi(), which stores the napi pointer\nin netdev_rx_queue.napi, and fbnic_reset_netif_napi() clears it again.\nBoth run under the netdev instance lock that the queue management ndos\nalso hold, so the pointer can be read directly.\n\nUse it and drop the divide.  The pointer is NULL exactly while the\ndatapath is down, so fbnic_queue_mem_alloc() can reject that case rather\nthan reaching into freed state: netdev_rx_queue_restart() calls it\nbefore it tests netif_running(), and fbnic_pm_suspend() leaves\nnetif_running() true across a PCIe recovery that never completes, so a\nqueue restart can arrive after fbnic_stop() has freed the rings and the\nvectors.  fbnic_stop() clears the association in\nfbnic_reset_netif_queues() before fbnic_free_napi_vectors(), so the\nNULL is always published first.  fbnic_queue_start() and\nfbnic_queue_stop() need no check of their own, as\nnetdev_rx_queue_reconfig() only reaches them once fbnic_queue_mem_alloc()\nhas succeeded under the same instance lock."}],"providerMetadata":{"dateUpdated":"2026-10-19T09:22:45.221Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/1fb569cf3bf97e552f465b2c719e36b48ae7c18b"},{"url":"https://git.kernel.org/stable/c/b5d9e9d4d0c13bc8b60d8d97e7a07fb25fea639e"}],"title":"eth: fbnic: use the Rx queue napi pointer to find the napi vector","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-98617","datePublished":"2026-10-18T15:19:37.060Z","dateReserved":"2026-09-25T10:25:14.360Z","dateUpdated":"2026-10-19T09:22:45.221Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-18 16:17:14","lastModifiedDate":"2026-10-19 10:19:25","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"98617","Ordinal":"1","Title":"eth: fbnic: use the Rx queue napi pointer to find the napi vecto","CVE":"CVE-2026-98617","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"98617","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\neth: fbnic: use the Rx queue napi pointer to find the napi vector\n\nThe queue management ndos pick the napi vector for an Rx queue with:\n\tnv = fbn->napi[idx % fbn->num_napi];\n\nThe issue is this is only correct in the cases where there are no\nstandalone Tx vectors. In those cases we were allocating the Tx vectors\nfirst and then the Rx so the queues would be pointing to Tx NAPI vectors\ninstead of the Rx ones.\n\nThe mapping the ndos want is already recorded.  fbnic_set_netif_napi()\npublishes it with netif_queue_set_napi(), which stores the napi pointer\nin netdev_rx_queue.napi, and fbnic_reset_netif_napi() clears it again.\nBoth run under the netdev instance lock that the queue management ndos\nalso hold, so the pointer can be read directly.\n\nUse it and drop the divide.  The pointer is NULL exactly while the\ndatapath is down, so fbnic_queue_mem_alloc() can reject that case rather\nthan reaching into freed state: netdev_rx_queue_restart() calls it\nbefore it tests netif_running(), and fbnic_pm_suspend() leaves\nnetif_running() true across a PCIe recovery that never completes, so a\nqueue restart can arrive after fbnic_stop() has freed the rings and the\nvectors.  fbnic_stop() clears the association in\nfbnic_reset_netif_queues() before fbnic_free_napi_vectors(), so the\nNULL is always published first.  fbnic_queue_start() and\nfbnic_queue_stop() need no check of their own, as\nnetdev_rx_queue_reconfig() only reaches them once fbnic_queue_mem_alloc()\nhas succeeded under the same instance lock.","Type":"Description","Title":"eth: fbnic: use the Rx queue napi pointer to find the napi vecto"}]}}}