Linux
bonding: alb: re-check primary_is_promisc under RTNL in bond_alb_monitor
In the Linux kernel, the following vulnerability has been resolved: bonding: alb: re-check primary_is_promisc under RTNL in bond_alb_monitor bond_alb_monitor() reads primary_is_promisc under RCU, then drops RCU and takes RTNL via rtnl_trylock() before undoing the promiscuity it set on the active slave. In that window the active slave can change under RTNL (RTM_DELLINK -> __bond_release_one() -> bond_alb_handle_active_change()), which already drops the promiscuity and clears primary_is_promisc. The monitor still acts on the stale decision: if the slave was removed with no failover, curr_active_slave is now NULL and the deref faults; if it failed over, the stale dev_set_promiscuity(-1) underflows the new slave's promiscuity counter and pins it in IFF_PROMISC. Oops: general protection fault, probably for non-canonical address ... KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] Workqueue: b42 bond_alb_monitor RIP: 0010:bond_alb_monitor (drivers/net/bonding/bond_alb.c:1600) process_one_work (kernel/workqueue.c:3322) worker_thread (kernel/workqueue.c:3486) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) Kernel panic - not syncing: Fatal exception Re-check primary_is_promisc (and curr_active_slave) after taking RTNL so the monitor only undoes an increment it still owns. The other bonding monitors already re-read state under RTNL in their commit phase (bond_miimon_commit/bond_ab_arp_commit); bond_alb_monitor() was the only one acting on the pre-trylock decision.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= d0e81b7e2246a41d068ecaf15aac9de570816d63, < f7668762bf5fd6db9397de5c0514407489d9d815
- >= d0e81b7e2246a41d068ecaf15aac9de570816d63, < 09add8d5cfa9c46828f51eaad162c36e86366b71
- >= d0e81b7e2246a41d068ecaf15aac9de570816d63, < b82f51681a7a88c7d3c865e817a3340d42b5fa2a
- >= d0e81b7e2246a41d068ecaf15aac9de570816d63, < dd148539fb4741d01c06b7d2c8bd84b01920756c
- >= d0e81b7e2246a41d068ecaf15aac9de570816d63, < dccec0227ed8d9e36936d66e256b957dc2858468
- >= d0e81b7e2246a41d068ecaf15aac9de570816d63, < 2faf75a8a06504071b4c0aea7e45a9cc49a4e187
- >= d0e81b7e2246a41d068ecaf15aac9de570816d63, < 257c4a3a34d8f51efb00f35375a0c6ce3c8f6ce2
- >= d0e81b7e2246a41d068ecaf15aac9de570816d63, < 683c6ba6e58e6ed1037831ea97dd58d9c0e76b8d
Fixed in f7668762bf5fd6db9397de5c0514407489d9d815, 09add8d5cfa9c46828f51eaad162c36e86366b71, b82f51681a7a88c7d3c865e817a3340d42b5fa2a, dd148539fb4741d01c06b7d2c8bd84b01920756c, dccec0227ed8d9e36936d66e256b957dc2858468, 2faf75a8a06504071b4c0aea7e45a9cc49a4e187, 257c4a3a34d8f51efb00f35375a0c6ce3c8f6ce2, 683c6ba6e58e6ed1037831ea97dd58d9c0e76b8d
- 2.6.24
Fixed in 0, 5.10.265, 5.15.216, 6.1.183, 6.6.152, 6.12.104, 6.18.45, 7.1.9, 7.2
Mitigation
Upgrade Linux to f7668762bf5fd6db9397de5c0514407489d9d815 or 09add8d5cfa9c46828f51eaad162c36e86366b71 or b82f51681a7a88c7d3c865e817a3340d42b5fa2a or dd148539fb4741d01c06b7d2c8bd84b01920756c or dccec0227ed8d9e36936d66e256b957dc2858468 or 2faf75a8a06504071b4c0aea7e45a9cc49a4e187 or 257c4a3a34d8f51efb00f35375a0c6ce3c8f6ce2 or 683c6ba6e58e6ed1037831ea97dd58d9c0e76b8d or later.
Upgrade Linux to 0 or 5.10.265 or 5.15.216 or 6.1.183 or 6.6.152 or 6.12.104 or 6.18.45 or 7.1.9 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.