CVE-2026-98074 — bonding: do not clear curr_active_slave prematurely when releasing all slaves
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).
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 0896341a44bf04bf6149d9307fe4686006f3eee1 and < b1ded242135071769902778dbab081e3fc09730f≥ 0896341a44bf04bf6149d9307fe4686006f3eee1 and < e39b203ec9e73852098d41b26386172d51babeb9≥ 0896341a44bf04bf6149d9307fe4686006f3eee1 and < 384739c631aa6749356ba062d6b7c9a484a733f6≥ 0896341a44bf04bf6149d9307fe4686006f3eee1 and < 7b435c69a30b40efc642de98b9bfa95fcf2ad4f0≥ 0896341a44bf04bf6149d9307fe4686006f3eee1 and < d6ef22e79c2be3612868daede0e9a84f05439d9e≥ 0896341a44bf04bf6149d9307fe4686006f3eee1 and < 19ba7ecfade159b3702c78a360fd7d971e2b7109≥ 0896341a44bf04bf6149d9307fe4686006f3eee1 and < 6d0ee411d5437f3d126ea6979acb83a8da29dc81≥ 0896341a44bf04bf6149d9307fe4686006f3eee1 and < af602c7aa5fedc9be3043244017aef4f26c96b70 and 1 moreversion 3.9 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Undergoing Analysis
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/d6ef22e79c2be3612868daede0e9a84f05439d9e
- git.kernel.org/stable/c/384739c631aa6749356ba062d6b7c9a484a733f6
- git.kernel.org/stable/c/e39b203ec9e73852098d41b26386172d51babeb9
- git.kernel.org/stable/c/af602c7aa5fedc9be3043244017aef4f26c96b70
- git.kernel.org/stable/c/b1ded242135071769902778dbab081e3fc09730f
- git.kernel.org/stable/c/7b435c69a30b40efc642de98b9bfa95fcf2ad4f0
- git.kernel.org/stable/c/6d0ee411d5437f3d126ea6979acb83a8da29dc81
- git.kernel.org/stable/c/19ba7ecfade159b3702c78a360fd7d971e2b7109
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 1d
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 1d
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 2d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 2d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 2d
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-98074 is "bonding: do not clear curr_active_slave prematurely when releasing all slaves", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.