nexthop: Forbid FDB status change while nexthop is in a group
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 38428d68719c454d269cb03b776d8a4b0ad66111 · < 8dd4aa0122885f710930de135af2adc4ccc3238f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nexthop: Forbid FDB status change while nexthop is in a group
The kernel forbids the creation of non-FDB nexthop groups with FDB nexthops:
# ip nexthop add id 1 via 192.0.2.1 fdb # ip nexthop add id 2 group 1 Error: Non FDB nexthop group cannot have fdb nexthops.
And vice versa:
# ip nexthop add id 3 via 192.0.2.2 dev dummy1 # ip nexthop add id 4 group 3 fdb Error: FDB nexthop group can only have fdb nexthops.
However, as long as no routes are pointing to a non-FDB nexthop group, the kernel allows changing the type of a nexthop from FDB to non-FDB and vice versa:
# ip nexthop add id 5 via 192.0.2.2 dev dummy1 # ip nexthop add id 6 group 5 # ip nexthop replace id 5 via 192.0.2.2 fdb # echo $? 0
From the CVE record · Linux
The Linux kernel allows a nexthop’s FDB status to change while it belongs to a group, creating an invalid configuration. Someone able to make that configuration change can trigger a kernel NULL pointer dereference when traffic uses the group; the input does not specify a network attack path or authentication requirements.
Engineers running Linux kernels that allow nexthop FDB status changes while a nexthop is in a group should check their systems; affected versions are not specified.