Answer in brief
CVE-2026-98277 records a Unknown severity vulnerability in eth: fbnic: ring the doorbell if a burst ends in a drop. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9a57bacd574b52b08bc2c600af6a8c7a87049ecf <60ef74357a36ed2a102a75bb68d37aa7f305b94e || >=9a57bacd574b52b08bc2c600af6a8c7a87049ecf <28fb764d670aa22dcbd2a02fd8fd87ae8d3563a9 || >=9a57bacd574b52b08bc2c600af6a8c7a87049ecf <490599ab23134962a6d18a024e84541d77bdb999 | 60ef74357a36ed2a102a75bb68d37aa7f305b94e, 28fb764d670aa22dcbd2a02fd8fd87ae8d3563a9, 490599ab23134962a6d18a024e84541d77bdb999 |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Oct 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 6, 2026
In the Linux kernel, the following vulnerability has been resolved: eth: fbnic: ring the doorbell if a burst ends in a drop fbnic_tx_map() skips the doorbell write, and the completion request, for every packet handed to it with xmit_more set, counting on the packet which ends the burst to publish them all. When that packet is dropped instead - skb_put_padto(), skb_cow_head() or a DMA mapping failure - nothing rings. The descriptors of the preceding packets stay invisible to the HW until the next transmit on that queue, which for a burst-then-idle workload may never come. Remember the meta descriptor of the last packet left without a doorbell and flush it from the error paths. The completion request has to be set on that descriptor rather than simply writing the tail, otherwise the HW would transmit the packets but never report a head, and the ring would fill up and stall for good. This is very similar to Joe's recent series of fixes for bnxt. Not seen in real life, reproduced under QEMU with failure injection.
Quoted source text, attributed separately from HOL analysis.