netfilter: flowtable: incorrect pppoe tuple
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netfilter: flowtable: incorrect pppoe tuple
pppoe traffic reaching ingress path does not match the flowtable entry because the pppoe header is expected to be at the network header offset. This bug causes a mismatch in the flow table lookup, so pppoe packets enter the classical forwarding path.
From the CVE record · Linux
The Linux kernel netfilter flowtable can look for a PPPoE header at the wrong offset, causing PPPoE traffic on the ingress path to miss its flowtable entry and take the classical forwarding path. The input does not describe an attacker action or specify authentication or user-interaction requirements.
Operators running the Linux kernel with netfilter flowtable and PPPoE traffic should check their deployments; affected versions are not specified.