CVE-2026-98618: Linux kernel · eth: fbnic: Handle maximum standalone channels
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 9843e5fabd6ab296df9c025b1d0e5bf79a6b8a08 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9843e5fabd6ab296df9c025b1d0e5bf79a6b8a08, 16ff1023213cc39c1a7ce737205c2a1a53c3a716, 6c903188b67617070017305a325fa326f270a43d +1
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to 9843e5fabd6ab296df9c025b1d0e5bf79a6b8a08, 16ff1023213cc39c1a7ce737205c2a1a53c3a716, 6c903188b67617070017305a325fa326f270a43d or 1f4c73064a50f53d596c6f1d06d2d700f43c4b32.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available in the Linux kernel as indicated by the fixed commit versions. Users and administrators should update to the patched kernel versions containing the referenced fixes to remediate this issue.
Description
A vulnerability in the Linux kernel's fbnic driver related to handling maximum standalone channels has been resolved. The issue arises because the allocation path for NAPI vectors excludes the maximum number of Tx queues, leading to NULL entries that are dereferenced during resource setup in configurations with 64 Tx and 64 Rx queues. This could cause instability or crashes. The fix includes properly accounting for the maximum vector count in standalone allocation.
References
- git.kernel.org/stable/c/9843e5fabd6ab296df9c025b1d0e5bf79a6b8a08 (opens in a new tab)
- git.kernel.org/stable/c/6c903188b67617070017305a325fa326f270a43d (opens in a new tab)
- git.kernel.org/stable/c/16ff1023213cc39c1a7ce737205c2a1a53c3a716 (opens in a new tab)
- git.kernel.org/stable/c/1f4c73064a50f53d596c6f1d06d2d700f43c4b32 (opens in a new tab)