octeontx2-af: fix VF bringup affecting PF promiscuous state
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 967db3529ecac305d230aa4e60abddf6ab63543a · < fabb881df322da25442f98d23f5fa371e3c78ec4| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
octeontx2-af: fix VF bringup affecting PF promiscuous state
Mbox handling of nix_set_rx_mode for a VF with promiscuous and all_multi flags set to false causes deletion of the PF's promiscuous and allmulti MCAM rules. This occurs because the APIs that enable/disable these rules operate only on the PF, even when the mbox request is made via a VF interface.
Guard both rvu_npc_enable_allmulti_entry() and rvu_npc_enable_promisc_entry() disable paths with an is_vf() check so that a VF bringing up or tearing down its interface cannot inadvertently clear the PF's MCAM rules.
From the CVE record · Linux
The Linux kernel’s octeontx2-af mailbox handling can delete a physical function’s (PF) promiscuous and all-multicast MCAM rules when a virtual function (VF) brings up or tears down its interface. This happens when the VF’s nix_set_rx_mode request has both promiscuous and all-multicast flags set to false.
Engineers running Linux kernels that use octeontx2-af with VFs should check whether their kernel includes the fix; affected versions were not specified.