Skip to main content
Vulnerability Database/CVE-2026-98616

CVE-2026-98616: Linux Kernel Use-After-Free Vulnerability

CVE-2026-98616 is a use-after-free flaw in the Linux kernel fbnic ethernet driver that can cause system crashes during power management operations. This post explains its technical details, impact, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-98616 Overview

CVE-2026-98616 is a NULL pointer dereference vulnerability in the Linux kernel's fbnic Ethernet driver. The flaw occurs because fbn->num_napi, the counter tracking live NAPI (New API) vectors, is not reset when those vectors are freed during the power management (PM) suspend path. If PCIe error recovery fails or the resume open path unwinds partway, the netdev continues running with num_napi > 0 while the napi[] array points at freed memory. A subsequent close triggers fbnic_dbg_down() to dereference the freed vectors and crash the kernel.

Critical Impact

Local kernel NULL pointer dereference in fbnic_dbg_down+0x28 leading to a system crash during PCIe error recovery or failed PM resume on affected systems.

Affected Products

  • Linux kernel builds containing the fbnic Meta Platforms Ethernet driver
  • Systems using Meta fbnic network interface cards with power management enabled
  • Hosts exercising PCIe error recovery paths on fbnic devices

Discovery Timeline

  • 2026-10-18 - CVE-2026-98616 published to NVD
  • 2026-10-19 - Last updated in NVD database

Technical Details for CVE-2026-98616

Vulnerability Analysis

The fbnic driver maintains fbn->num_napi as the count of live NAPI vectors, each owning an IRQ. During PM suspend, fbnic_pm_suspend() tears down the datapath via ndo_stop() and frees the IRQs. However, it leaves netif_running() as true so the resume path knows to re-open the device.

On resume, __fbnic_pm_resume() rebuilds the datapath, fbnic_reset_queues() sets num_napi, and __fbnic_open() reallocates the vectors. Two failure scenarios leave the datapath torn down without rebuild while num_napi still references freed vectors. A PCIe error recovery failure in fbnic_err_slot_reset() causes __fbnic_pm_resume() to return an error with PCI_ERS_RESULT_DISCONNECT, so .resume never runs. Alternatively, __fbnic_open() can fail partway during resume and unwind, freeing vectors after fbnic_reset_queues() already assigned num_napi.

Root Cause

The root cause is a state inconsistency between the num_napi counter and the backing napi[] array during error paths. When vectors are freed, the count is not cleared, violating the invariant that num_napi reflects live vector allocations. Subsequent remove or unbind operations call fbnic_down() and fbnic_dbg_down(), which iterate using num_napi and dereference freed memory at address 0x210.

Attack Vector

This vulnerability requires local conditions involving PCIe hardware faults or PM resume failures on systems with the fbnic driver loaded. It is not a remotely exploitable flaw. The impact is a kernel NULL pointer dereference crash. Refer to the upstream fixes in Linux Kernel Commit 4bcc4a92, Linux Kernel Commit 4f4b767f, and Linux Kernel Commit c5b5aee4 for technical details.

Detection Methods for CVE-2026-98616

Indicators of Compromise

  • Kernel log entries containing BUG: kernel NULL pointer dereference, address: 0000000000000210
  • Call traces including fbnic_dbg_down+0x28 or fbnic_down() during device remove or unbind operations
  • Preceding dmesg messages indicating PCIe error recovery failure on an fbnic device or __fbnic_open() failures during resume from suspend

Detection Strategies

  • Monitor kernel ring buffer and journald for NULL pointer dereference oops originating in the fbnic module after suspend/resume cycles or PCIe AER events
  • Correlate PCI_ERS_RESULT_DISCONNECT events on fbnic PCIe slots with subsequent system crashes
  • Audit running kernel versions against the fixed stable commits listed above

Monitoring Recommendations

  • Collect /var/log/kern.log and dmesg output from hosts with fbnic NICs and forward to centralized logging for crash pattern analysis
  • Alert on repeated PM resume failures or PCIe error recovery events on fbnic interfaces
  • Track kernel panic and oops telemetry from Linux endpoints to identify affected systems before they are power-cycled and lose volatile evidence

How to Mitigate CVE-2026-98616

Immediate Actions Required

  • Apply the stable kernel updates containing commits 4bcc4a92, 4f4b767f, and c5b5aee4 to all Linux hosts using the fbnic driver
  • Inventory systems with Meta fbnic NICs and schedule maintenance windows for kernel upgrades
  • Review PCIe AER logs on affected hardware to identify systems experiencing the failure path

Patch Information

The fix clears num_napi when the vectors are freed in the suspend teardown path and on resume open failure. A good resume re-establishes the counter before __fbnic_open() runs. The normal ndo_stop() down/up cycle is unchanged and keeps num_napi for the next ndo_open(). See Linux Kernel Commit 4bcc4a92, Linux Kernel Commit 4f4b767f, and Linux Kernel Commit c5b5aee4.

Workarounds

  • Avoid suspend/resume cycles on hosts using the fbnic driver until the kernel patch is deployed
  • Where possible, disable PM suspend on servers equipped with fbnic NICs via systemd systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target
  • Replace or disable fbnic NICs on hosts that cannot be patched or reconfigured for suspend policy changes

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.