---
id: CVE-2026-98074
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  bonding: do not clear curr_active_slave prematurely when releasing all slaves

  When releasing all slaves during bond destruction (all == true),
  __bond_release_one() unc…
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  bonding: do not clear curr_active_slave prematurely when releasing all slaves

  When releasing all slaves during bond destruction (all == true),
  __bond_release_one() unc…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 0896341a44bf04bf6149d9307fe4686006f3eee1 <
    d6ef22e79c2be3612868daede0e9a84f05439d9e
  - >-
    Linux >= 0896341a44bf04bf6149d9307fe4686006f3eee1 <
    19ba7ecfade159b3702c78a360fd7d971e2b7109
  - >-
    Linux >= 0896341a44bf04bf6149d9307fe4686006f3eee1 <
    6d0ee411d5437f3d126ea6979acb83a8da29dc81
  - >-
    Linux >= 0896341a44bf04bf6149d9307fe4686006f3eee1 <
    af602c7aa5fedc9be3043244017aef4f26c96b70
  - Linux 3.9
published: '2026-09-25'
updated: '2026-09-25'
sourceUpdated: '2026-09-25T11:17:36.730'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-98074'
references:
  - url: 'https://git.kernel.org/stable/c/19ba7ecfade159b3702c78a360fd7d971e2b7109'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/6d0ee411d5437f3d126ea6979acb83a8da29dc81'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/af602c7aa5fedc9be3043244017aef4f26c96b70'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/d6ef22e79c2be3612868daede0e9a84f05439d9e'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-25T11:06:38.839Z'
---

## Overview

In the Linux kernel, the following vulnerability has been resolved:

bonding: do not clear curr_active_slave prematurely when releasing all slaves

When releasing all slaves during bond destruction (all == true),
__bond_release_one() unconditionally clears bond->curr_active_slave to
NULL in every iteration.

If a backup slave is released before the active slave,
bond_alb_deinit_slave() triggers rlb_teach_disabled_mac_on_primary(),
which increments the active slave dev promiscuity counter and sets
bond_info->primary_is_promisc = 1.

Because bond->curr_active_slave was prematurely cleared to NULL when
releasing the backup slave, the subsequent iteration releasing the active
slave evaluates oldcurrent as NULL, so bond_change_active_slave(bond, NULL)
is skipped. Consequently, bond_alb_handle_active_change() is never called
to decrement the promiscuity counter, permanently leaking promiscuous
mode on the physical device after bond teardown.

When oldcurrent == slave, bond_change_active_slave(bond, NULL) already sets
bond->curr_active_slave to NULL. We only need to avoid selecting a new
active slave when all == true. Replace the if (all) branch with
if (!all && oldcurrent == slave).

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.