CVE-2026-98074: Linux kernel · bonding: do not clear curr_active_slave prematurely when releasing all slaves
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 26 Oct 2026, 17:16 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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).
References
- ubuntu.com/security/CVE-2026-98074 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-98074 (opens in a new tab)
- git.kernel.org/stable/c/d6ef22e79c2be3612868daede0e9a84f05439d9e (opens in a new tab)
- git.kernel.org/stable/c/6d0ee411d5437f3d126ea6979acb83a8da29dc81 (opens in a new tab)
- git.kernel.org/stable/c/af602c7aa5fedc9be3043244017aef4f26c96b70 (opens in a new tab)
- git.kernel.org/stable/c/19ba7ecfade159b3702c78a360fd7d971e2b7109 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-98074 (opens in a new tab)
- git.kernel.org/stable/c/384739c631aa6749356ba062d6b7c9a484a733f6 (opens in a new tab)
- git.kernel.org/stable/c/7b435c69a30b40efc642de98b9bfa95fcf2ad4f0 (opens in a new tab)
- git.kernel.org/stable/c/b1ded242135071769902778dbab081e3fc09730f (opens in a new tab)
- git.kernel.org/stable/c/e39b203ec9e73852098d41b26386172d51babeb9 (opens in a new tab)