CVE-2026-98277
Last modified
CVE-2026-98277 is a vulnerability of currently unknown severity. 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.
Description
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 9a57bacd574b52b08bc2c600af6a8c7a87049ecf, < 60ef74357a36ed2a102a75bb68d37aa7f305b94e; >= 9a57bacd574b52b08bc2c600af6a8c7a87049ecf, < 28fb764d670aa22dcbd2a02fd8fd87ae8d3563a9; >= 9a57bacd574b52b08bc2c600af6a8c7a87049ecf, < 490599ab23134962a6d18a024e84541d77bdb999 |
| Linux | Linux | 6.11 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98277?
How severe is CVE-2026-98277?
How do I fix CVE-2026-98277?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98271In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98272In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98273In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98274In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98275In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98276In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-98278In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98279In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9828Deserialization of untrusted data vulnerability in QOS.CH Sa…2.9
- CVE-2026-98280In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98281In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-98282In the Linux kernel, the following vulnerability has been re…8.8
Are you affected by CVE-2026-98277?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
