CVE-2026-98074
Medium 5.5No known exploitationFix availablebonding: do not clear curr_active_slave prematurely when releasing all slaves
Record last updated
CVSS score
Medium on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 2% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
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).
Weakness: CWE-404
Patching and mitigation
- Patch status
- Fix available (source: NVD (reference tagged Patch))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- msrc.microsoft.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Microsoft | azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Not documented | 6.6.158.1-1 | Microsoft MSRC |
| Microsoft | azl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0 | Not documented | 0:6.18.57-1.1.azl4 | Microsoft MSRC |
| linux | linux_kernel | from 3.9 before 5.10.271 | 5.10.271 | NIST NVD |
| linux | linux_kernel | from 5.11 before 5.15.222 | 5.15.222 | NIST NVD |
| linux | linux_kernel | from 5.16 before 6.1.189 | 6.1.189 | NIST NVD |
| linux | linux_kernel | from 6.13 before 6.18.53 | 6.18.53 | NIST NVD |
| linux | linux_kernel | from 6.19 before 7.2.7 | 7.2.7 | NIST NVD |
| linux | linux_kernel | from 6.2 before 6.6.158 | 6.6.158 | NIST NVD |
| linux | linux_kernel | from 6.7 before 6.12.111 | 6.12.111 | NIST NVD |
| linux | linux_kernel | 7.3 | Not documented | NIST NVD |
Timeline
Advisory
Microsoft advisory published
Advisory change
Microsoft advisory revised (2.0): Information published.
Advisory change
Microsoft advisory revised (3.0): Information published.
Advisory change
Microsoft advisory revised (4.0): Information published.
Advisory change
Microsoft advisory revised (5.0): Information published.
Patch
Fix documented by NVD (reference tagged Patch)
Vendor guidance and references
- https://git.kernel.org/stable/c/19ba7ecfade159b3702c78a360fd7d971e2b7109 (opens in a new tab)patch
- https://git.kernel.org/stable/c/384739c631aa6749356ba062d6b7c9a484a733f6 (opens in a new tab)patch
- https://git.kernel.org/stable/c/6d0ee411d5437f3d126ea6979acb83a8da29dc81 (opens in a new tab)patch
- https://git.kernel.org/stable/c/7b435c69a30b40efc642de98b9bfa95fcf2ad4f0 (opens in a new tab)patch
- https://git.kernel.org/stable/c/af602c7aa5fedc9be3043244017aef4f26c96b70 (opens in a new tab)patch
- https://git.kernel.org/stable/c/b1ded242135071769902778dbab081e3fc09730f (opens in a new tab)patch
- https://git.kernel.org/stable/c/d6ef22e79c2be3612868daede0e9a84f05439d9e (opens in a new tab)patch
- https://git.kernel.org/stable/c/e39b203ec9e73852098d41b26386172d51babeb9 (opens in a new tab)patch
- Microsoft Security Update Guide (opens in a new tab)vendor-advisory