CVE-2026-98074

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).

Gravité et risque d'exploitation

CVE-2026-98074 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.18 %, ce qui la place devant 6.7 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions <384739c631aa6749356ba062d6b7c9a484a733f6, <=6.1.*, <=6.12.*, 7.2.7, 6.18.53, 0, <d6ef22e79c2be3612868daede0e9a84f05439d9e, <b1ded242135071769902778dbab081e3fc09730f, <3.9, <6d0ee411d5437f3d126ea6979acb83a8da29dc81, <19ba7ecfade159b3702c78a360fd7d971e2b7109, 5.10.271, 6.6.158, <=5.10.*, <=6.6.*, 6.1.189, <=6.18.*, <af602c7aa5fedc9be3043244017aef4f26c96b70, 5.15.222, <7b435c69a30b40efc642de98b9bfa95fcf2ad4f0, 7.3, <=7.2.*, 0896341a44bf04bf6149d9307fe4686006f3eee1, <=*, <e39b203ec9e73852098d41b26386172d51babeb9, <=5.15.*, 6.12.111, 3.9) est présent sur votre parc.
• Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
• À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
• Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

• https://git.kernel.org/stable/c/b1ded242135071769902778dbab081e3fc09730f
• https://git.kernel.org/stable/c/e39b203ec9e73852098d41b26386172d51babeb9
• https://git.kernel.org/stable/c/384739c631aa6749356ba062d6b7c9a484a733f6
• https://git.kernel.org/stable/c/7b435c69a30b40efc642de98b9bfa95fcf2ad4f0
• https://git.kernel.org/stable/c/d6ef22e79c2be3612868daede0e9a84f05439d9e
• https://git.kernel.org/stable/c/19ba7ecfade159b3702c78a360fd7d971e2b7109
• https://git.kernel.org/stable/c/6d0ee411d5437f3d126ea6979acb83a8da29dc81
• https://git.kernel.org/stable/c/af602c7aa5fedc9be3043244017aef4f26c96b70