CVE-2026-98074
CVE CVE-2026-98074EUVD EUVD-2026-86727Published 2026-09-25T10:24:13.000Z
What the advisory describes
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).
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 0896341a44bf04bf6149d9307fe4686006f3eee1 <af602c7aa5fedc9be3043244017aef4f26c96b70; 0896341a44bf04bf6149d9307fe4686006f3eee1 <6d0ee411d5437f3d126ea6979acb83a8da29dc81; patch: 7.2.7; 3.9; patch: 6.12.111; patch: 0; patch: 7.3-rc2; 0896341a44bf04bf6149d9307fe4686006f3eee1 <19ba7ecfade159b3702c78a360fd7d971e2b7109; 0896341a44bf04bf6149d9307fe4686006f3eee1 <d6ef22e79c2be3612868daede0e9a84f05439d9e; patch: 6.18.53
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.