In the Linux kernel, the following vulnerability has been resolved: eth: fbnic: use the Rx queue napi pointer to find the napi vector The queue… (CVE-2026-98617)
Description
A vulnerability in the Linux kernel's fbnic Ethernet driver related to incorrect usage of the Rx queue NAPI pointer has been resolved. The issue involved the queue management code incorrectly mapping Rx queues to Tx NAPI vectors when standalone Tx vectors were present, potentially causing use of freed memory or invalid pointers during queue restart or PCIe recovery scenarios. The fix uses the correct napi pointer stored in netdev_rx_queue.napi, ensuring safe queue management under locking. No CVSS score is available for this issue.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel fbnic Ethernet driver had a vulnerability where the Rx queue management incorrectly selected the NAPI vector by using an index-based modulo operation, which was only valid when no standalone Tx vectors existed. In cases with standalone Tx vectors, Rx queues pointed to Tx NAPI vectors, leading to potential use-after-free or invalid pointer dereferences during queue restarts or PCIe recovery. The fix involves using the napi pointer directly stored in netdev_rx_queue.napi, which is properly synchronized under the netdev instance lock, eliminating the incorrect indexing and preventing access to freed resources.
Potential Impact
The vulnerability could lead to kernel instability or crashes due to dereferencing invalid or freed pointers in the network driver during queue restarts or PCIe recovery. This could impact system reliability and network functionality on affected Linux kernel versions using the fbnic driver. There is no indication of remote code execution or privilege escalation from the provided data.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to correct the NAPI vector mapping in the fbnic driver. Users should apply the official kernel updates that include this fix. Since this is a kernel-level issue, upgrading to a patched kernel version is the recommended remediation. No additional mitigations are indicated or required based on the vendor advisory.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-j327-5j79-p464
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-98617"]
Threat ID: 6ad520ae2cdf04f656993a79
Added to database: 10/18/2026, 19:40:30 UTC
Last enriched: 10/18/2026, 21:33:13 UTC
Last updated: 10/18/2026, 23:48:12 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.