batman-adv: clean untagged VLAN on netdev registration failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5d2c05b213377694a2aa8ce1ed9b23f7c39b0569 · < c945f6007e7851e74706c72f98763023699bcd97| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
batman-adv: clean untagged VLAN on netdev registration failure
When an mesh interface is registered, it creates an untagged struct batadv_meshif_vlan on top of it via the NETDEV_REGISTER notifier. But in this process, another receiver of this notification can veto the registration. The netdev registration will be aborted because of this veto.
The register_netdevice() call will try to clean up the net_device using unregister_netdevice_queue() - which only uses the .priv_destructor to free private resources. In this situation, .dellink will not be called.
The cleanup of the untagged batadv_meshif_vlan must thefore be done in the destructor to avoid a leak of this object.
From the CVE record · Linux
The Linux kernel's batman-adv component can leak an untagged VLAN object if another notification receiver vetoes mesh interface registration. The input does not describe how an attacker could trigger this condition or specify network access, authentication, or user-interaction requirements.
Engineers running the Linux kernel with batman-adv should check their installations; affected versions are not specified.