net: bridge: fix vlan tunnel dst null pointer dereference
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 11538d039ac6efcf4f1a6c536e1b87cd3668a9fd · < 58e2071742e38f29f051b709a5cca014ba51166f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: bridge: fix vlan tunnel dst null pointer dereference
This patch fixes a tunnel_dst null pointer dereference due to lockless access in the tunnel egress path. When deleting a vlan tunnel the tunnel_dst pointer is set to NULL without waiting a grace period (i.e. while it's still usable) and packets egressing are dereferencing it without checking. Use READ/WRITE_ONCE to annotate the lockless use of tunnel_id, use RCU for accessing tunnel_dst and make sure it is read only once and checked in the egress path. The dst is already properly RCU protected so we don't need to do anything fancy than to make sure tunnel_id and tunnel_dst are read only once and checked in the egress path.
From the CVE record · Linux
The Linux kernel bridge VLAN tunnel egress path can dereference a null tunnel destination pointer. This can occur when a VLAN tunnel is deleted while packets are egressing. The input does not specify whether an attacker can trigger the condition or what access would be required.
Operators running the Linux kernel with bridge VLAN tunnels should check their installations; affected versions are not specified.