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

CVE-2026-98074: Linux Kernel Bonding Privilege Escalation

CVE-2026-98074 is a privilege escalation flaw in Linux kernel bonding that causes promiscuous mode leakage during bond teardown. This post explains its technical details, affected versions, impact, and mitigation steps.

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-98074 Overview

CVE-2026-98074 is a Linux kernel vulnerability in the bonding driver. The flaw affects the __bond_release_one() function during bond destruction when all slaves are released. The driver prematurely clears bond->curr_active_slave to NULL in every iteration, breaking the active slave teardown path. This causes bond_alb_handle_active_change() to be skipped, leaking promiscuous mode on the underlying physical device after bond teardown.

Critical Impact

The bonding driver permanently leaks promiscuous mode on the physical network device after bond destruction, altering network behavior and potentially exposing additional traffic to the host.

Affected Products

  • Linux kernel bonding driver (drivers/net/bonding)
  • Kernel builds using Adaptive Load Balancing (ALB) mode with backup and active slaves
  • Systems that create and destroy bonding interfaces at runtime

Discovery Timeline

  • 2026-09-25 - CVE-2026-98074 published to NVD
  • 2026-09-30 - Last updated in NVD database

Technical Details for CVE-2026-98074

Vulnerability Analysis

The bonding driver aggregates multiple network interfaces into a single logical interface. During bond destruction, __bond_release_one() is invoked with all == true and iterates over every slave to release it. In each iteration the function unconditionally sets bond->curr_active_slave to NULL, regardless of whether the current slave being released is actually the active one.

When a backup slave is released before the active slave in Adaptive Load Balancing (ALB) mode, bond_alb_deinit_slave() invokes rlb_teach_disabled_mac_on_primary(). That helper increments the promiscuity counter on the active slave device and sets bond_info->primary_is_promisc = 1. The driver expects a later call to bond_alb_handle_active_change() to decrement the counter and restore the original mode.

Because bond->curr_active_slave was already nulled out when the backup slave was released, the subsequent iteration releasing the active slave sees oldcurrent == NULL. The branch calling bond_change_active_slave(bond, NULL) is skipped, bond_alb_handle_active_change() is never invoked, and the promiscuity counter is never decremented.

Root Cause

The root cause is an incorrect control-flow condition in __bond_release_one(). The function clears bond->curr_active_slave in every teardown iteration instead of only when the slave being released is the current active slave. The fix replaces the if (all) branch with if (!all && oldcurrent == slave) so that selection of a new active slave is only skipped when all slaves are being released, while allowing the normal teardown path to run on the active slave.

Attack Vector

The condition is triggered by local operations that create and tear down bonding interfaces configured in ALB mode with at least one backup and one active slave. There is no network-reachable attack surface. The practical impact is a persistent promiscuous mode leak on the physical network device after bond destruction, which can alter packet reception semantics and leave the host accepting frames it would normally drop.

The vulnerability is described in detail in the upstream commits. See Kernel Git Commit af602c7aa5fe for the primary fix.

Detection Methods for CVE-2026-98074

Indicators of Compromise

  • Physical network devices reporting the PROMISC flag after a bond interface has been destroyed with ip link delete bondX.
  • Unexpected non-zero promiscuity counters in /sys/class/net/<dev>/flags or ip -d link show <dev> output on former bond slaves.
  • Repeated bond create/destroy cycles correlated with monotonically increasing promiscuity state on physical NICs.

Detection Strategies

  • Audit kernel versions against the fixed commits listed in the upstream references and flag hosts running vulnerable kernels with bonding in ALB mode.
  • Script periodic checks that enumerate interfaces no longer enslaved to a bond and verify none retain PROMISC unexpectedly.
  • Review system logs for bonding: messages around interface teardown to correlate release order of backup vs. active slaves.

Monitoring Recommendations

  • Collect interface flag telemetry from endpoints and servers using bonding and alert on persistent promiscuous mode outside of defined packet-capture workflows.
  • Track kernel versions and bonding mode configuration in configuration management to prioritize patching for ALB deployments.
  • Correlate bond lifecycle events (create, enslave, release, delete) with downstream device flag state to catch leaked state early.

How to Mitigate CVE-2026-98074

Immediate Actions Required

  • Update to a Linux kernel version that includes the upstream bonding fix referenced in the stable commits for this CVE.
  • Inventory systems using the bonding driver in ALB mode and prioritize them for patching.
  • Avoid repeated runtime bond teardown on unpatched hosts, and reboot affected hosts after patching to clear any leaked promiscuous state.

Patch Information

The fix replaces the unconditional if (all) branch in __bond_release_one() with if (!all && oldcurrent == slave), allowing bond_change_active_slave(bond, NULL) to run when the active slave itself is released. Patches are available in the following upstream stable commits: 19ba7ecfade1, 6d0ee411d543, af602c7aa5fe, and d6ef22e79c2b.

Workarounds

  • Avoid dynamic destruction of bonds configured in ALB mode on unpatched kernels; prefer configuring bonds at boot and leaving them in place.
  • If a bond must be destroyed, manually clear residual promiscuous state on former slave interfaces using ip link set <dev> promisc off after verifying no legitimate packet-capture process requires it.
  • Reboot affected hosts after bond teardown to guarantee the physical device returns to its intended flag state until the kernel patch is applied.

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.