batman-adv: v: stop OGMv2 on disabled interface
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0da0035942d47766c32843143fb5dba7a29cb48c · < 1be1e99cbd5b74a69d3f92200ca87cf1bce852db| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
batman-adv: v: stop OGMv2 on disabled interface
When a batadv_hard_iface is disabled, its mesh_iface pointer is set to NULL. However, batadv_v_ogm_send_meshif() may still dispatch OGMs via batadv_v_ogm_queue_on_if() for interfaces that have since lost their mesh_iface association. This results in a NULL pointer dereference when batadv_v_ogm_queue_on_if() unconditionally calls netdev_priv() on the now NULL hard_iface->mesh_iface to retrieve the batadv_priv.
It is necessary to ensure that the batadv_v_ogm_queue_on_if() checks that it is using the same mesh_iface for which batadv_v_ogm_send_meshif() was called.
From the CVE record · Linux
In the Linux kernel's batman-adv component, OGMv2 processing can dereference a NULL pointer if a hard interface loses its mesh-interface association while messages are being dispatched. This can cause a kernel fault. The input does not specify how an attacker could trigger it, whether authentication is needed, or whether user interaction is required.
Engineers running Linux kernels with batman-adv should check their installations; affected versions are not specified.