CVE-2026-98277: Linux kernel · eth: fbnic: ring the doorbell if a burst ends in a drop
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 490599ab23134962a6d18a024e84541d77bdb999 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 490599ab23134962a6d18a024e84541d77bdb999, 60ef74357a36ed2a102a75bb68d37aa7f305b94e, 28fb764d670aa22dcbd2a02fd8fd87ae8d3563a9
Exploitation evidence
Disclosed: evidence found.
CVE published 6 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 490599ab23134962a6d18a024e84541d77bdb999, 60ef74357a36ed2a102a75bb68d37aa7f305b94e or 28fb764d670aa22dcbd2a02fd8fd87ae8d3563a9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented and merged into the Linux kernel. Users should update to the fixed kernel versions containing commits 490599ab23134962a6d18a024e84541d77bdb999, 60ef74357a36ed2a102a75bb68d37aa7f305b94e, or 28fb764d670aa22dcbd2a02fd8fd87ae8d3563a9. No additional mitigation is required beyond applying the official patch.
Description
A vulnerability in the Linux kernel's fbnic network driver causes the hardware doorbell not to ring if a burst of packets ends with a dropped packet. This results in the hardware not being notified of preceding packets, potentially causing the transmit ring to fill up and stall. The issue was reproduced under QEMU with failure injection but has not been observed in real-world scenarios. A fix has been implemented in the Linux kernel.