bonding: do not clear curr_active_slave prematurely when releasing all slaves
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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() 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).
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 0896341a44bf04bf6149d9307fe4686006f3eee1 · fixed in b1ded242135071769902778dbab081e3fc09730f; From 0896341a44bf04bf6149d9307fe4686006f3eee1 · fixed in e39b203ec9e73852098d41b26386172d51babeb9; From 0896341a44bf04bf6149d9307fe4686006f3eee1 · fixed in 384739c631aa6749356ba062d6b7c9a484a733f6; From 0896341a44bf04bf6149d9307fe4686006f3eee1 · fixed in 7b435c69a30b40efc642de98b9bfa95fcf2ad4f0; From 0896341a44bf04bf6149d9307fe4686006f3eee1 · fixed in d6ef22e79c2be3612868daede0e9a84f05439d9e; From 0896341a44bf04bf6149d9307fe4686006f3eee1 · fixed in 19ba7ecfade159b3702c78a360fd7d971e2b7109; From 0896341a44bf04bf6149d9307fe4686006f3eee1 · fixed in 6d0ee411d5437f3d126ea6979acb83a8da29dc81; From 0896341a44bf04bf6149d9307fe4686006f3eee1 · fixed in af602c7aa5fedc9be3043244017aef4f26c96b70
- Linux Linux
3.9
- KernelLinux
From 3.9.0 · fixed in 5.10.271; From 5.11.0 · fixed in 5.15.222; From 5.16.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.111; From 6.13.0 · fixed in 6.18.53; From 6.19.0 · fixed in 7.2.7
References 8
git.kernel.org
- stable/c/b1ded242135071769902778dbab081e3fc09730f
- stable/c/e39b203ec9e73852098d41b26386172d51babeb9
- stable/c/384739c631aa6749356ba062d6b7c9a484a733f6
- stable/c/7b435c69a30b40efc642de98b9bfa95fcf2ad4f0
- stable/c/d6ef22e79c2be3612868daede0e9a84f05439d9e
- stable/c/19ba7ecfade159b3702c78a360fd7d971e2b7109
- stable/c/6d0ee411d5437f3d126ea6979acb83a8da29dc81
- stable/c/af602c7aa5fedc9be3043244017aef4f26c96b70